MIMO Enhancement Capability Design

ABSTRACT

Apparatuses, systems, and methods for multi-TRP by a UE, including out of order delivery of PDSCH, PUSCH, and/or DL ACK/NACK. The UE may receive, from a base station, a configuration that may include multiple control resource set (CORESET) pools and each CORESET pool may be associated with an index value. The UE may determine that at least two DCIs of the multiple DCIs end at a common symbol and determine, based on one or more predetermined rules, when the UE may be scheduled to receive PDSCHs, transmit PUSCHs, and/or transmit ACK/NACKs from CORESETs associated with the at least two DCIs.

PRIORITY DATA

This application is the National Stage of International Application No.PCT/CN2020/074912, filed Feb. 12, 2020, which is hereby incorporated byreference in its entirety as though fully and completely set forthherein.

FIELD

The present application relates to wireless devices, and moreparticularly to apparatuses, systems, and methods for multipletransmission and reception (multi-TRP) by a user equipment device (UE),including out of order delivery of PDSCH, PUSCH, and/or DL ACK/NACK.

DESCRIPTION OF THE RELATED ART

Wireless communication systems are rapidly growing in usage. In recentyears, wireless devices such as smart phones and tablet computers havebecome increasingly sophisticated. In addition to supporting telephonecalls, many mobile devices now provide access to the internet, email,text messaging, and navigation using the global positioning system(GPS), and are capable of operating sophisticated applications thatutilize these functionalities.

Long Term Evolution (LTE) has become the technology of choice for themajority of wireless network operators worldwide, providing mobilebroadband data and high-speed Internet access to their subscriber base.LTE defines a number of downlink (DL) physical channels, categorized astransport or control channels, to carry information blocks received frommedium access control (MAC) and higher layers. LTE also defines a numberof physical layer channels for the uplink (UL).

For example, LTE defines a Physical Downlink Shared Channel (PDSCH) as aDL transport channel. The PDSCH is the main data-bearing channelallocated to users on a dynamic and opportunistic basis. The PDSCHcarries data in Transport Blocks (TB) corresponding to a MAC protocoldata unit (PDU), passed from the MAC layer to the physical (PHY) layeronce per Transmission Time Interval (TTI). The PDSCH is also used totransmit broadcast information such as System Information Blocks (SIB)and paging messages.

As another example, LTE defines a Physical Downlink Control Channel(PDCCH) as a DL control channel that carries the resource assignment forUEs that are contained in a Downlink Control Information (DCI) message.Multiple PDCCHs can be transmitted in the same subframe using ControlChannel Elements (CCE), each of which is a nine set of four resourceelements known as Resource Element Groups (REG). The PDCCH employsquadrature phase-shift keying (QPSK) modulation, with four QPSK symbolsmapped to each REG. Furthermore, 1, 2, 4, or 8 CCEs can be used for aUE, depending on channel conditions, to ensure sufficient robustness.

Additionally, LTE defines a Physical Uplink Shared Channel (PUSCH) as aUL channel shared by all devices (user equipment, UE) in a radio cell totransmit user data to the network. The scheduling for all UEs is undercontrol of the LTE base station (enhanced Node B, or eNB). The eNB usesthe uplink scheduling grant (DCI format 0) to inform the UE aboutresource block (RB) assignment, and the modulation and coding scheme tobe used. PUSCH typically supports QPSK and quadrature amplitudemodulation (QAM). In addition to user data, the PUSCH also carries anycontrol information necessary to decode the information, such astransport format indicators and multiple-in multiple-out (MIMO)parameters. Control data is multiplexed with information data prior todigital Fourier transform (DFT) spreading.

A proposed next telecommunications standard moving beyond the currentInternational Mobile Telecommunications-Advanced (IMT-Advanced)Standards is called 5th generation mobile networks or 5th generationwireless systems, or 5G for short (otherwise known as 5G-NR for 5G NewRadio, also simply referred to as NR). 5G-NR proposes a higher capacityfor a higher density of mobile broadband users, also supportingdevice-to-device, ultra-reliable, and massive machine communications, aswell as lower latency and lower battery consumption, than current LTEstandards. Further, the 5G-NR standard may allow for less restrictive UEscheduling as compared to current LTE standards. Consequently, effortsare being made in ongoing developments of 5G-NR to take advantage ofhigher throughputs possible at higher frequencies.

SUMMARY

Embodiments relate to apparatuses, systems, and methods multipletransmission and reception (multi-TRP) by a user equipment device (UE),including out of order delivery of PDSCH, PUSCH, and/or DL ACK/NACK.

In some embodiments, a wireless device, e.g., such as a user equipmentdevice (UE), may be configured to receive, from a base station, aconfiguration that may include multiple control resource set (CORESET)pools. In some embodiments, each CORESET pool may be associated with anindex value, e.g., a CORESETPool index. The UE may be configured todetermine that at least two DCIs of the multiple DCIs end at a commonsymbol and determine, based on one or more predetermined rules, when theUE may be scheduled to receive physical downlink control channels(PDSCHs), transmit physical uplink control channels (PUSCHs), and/ortransmit acknowledgments/negative acknowledgments (ACK/NACKs) fromCORESETs associated with the at least two DCIs. In some embodiments, theUE may determine a possible relationship between the PDSCHs associatedwith the at least 2 DCIs based on a first predetermined rule, e.g., anearliest possible starting/ending symbol of one PDSCH relative toanother PDSCH. In some embodiments, the first predetermined rule mayinclude at least one of no overlap between PDSCHs (e.g., a startingsymbol of one PDSCH does not occur until after an ending symbol ofanother PDSCH) or at least partial overlap between PDSCHs (e.g., astarting symbol of one PDSCH occurs prior to an ending symbol of anotherPDSCH). In some embodiments, the UE may determine a possiblerelationship between the PUSCHs associated with the at least 2 DCIsbased on a second predetermined rule, e.g., an earliest possiblestarting/ending symbol of one PUSCH relative to another PUSCH. In someembodiments, the second predetermined rule may include at least one ofno overlap between PUSCHs (e.g., a starting symbol of one PUSCH does notoccur until after an ending symbol of another PUSCH) or at least partialoverlap between PUSCHs (e.g., a starting symbol of one PUSCH occursprior to an ending symbol of another PUSCH). In some embodiments, the UEmay determine a possible relationship between ACK/NACKS for PDSCHsassociated with the at least 2 DCIs based on a third predetermined rule.

The techniques described herein may be implemented in and/or used with anumber of different types of devices, including but not limited tocellular phones, tablet computers, wearable computing devices, portablemedia players, and any of various other computing devices.

This Summary is intended to provide a brief overview of some of thesubject matter described in this document. Accordingly, it will beappreciated that the above-described features are merely examples andshould not be construed to narrow the scope or spirit of the subjectmatter described herein in any way. Other features, aspects, andadvantages of the subject matter described herein will become apparentfrom the following Detailed Description, Figures, and Claims.

BRIEF DESCRIPTION OF THE DRAWINGS

A better understanding of the present subject matter can be obtainedwhen the following detailed description of various embodiments isconsidered in conjunction with the following drawings, in which:

FIG. 1A illustrates an example wireless communication system accordingto some embodiments.

FIG. 1B illustrates an example of a base station (BS) and an accesspoint in communication with a user equipment (UE) device according tosome embodiments.

FIG. 2 illustrates an example simplified block diagram of a WLAN AccessPoint (AP), according to some embodiments.

FIG. 3 illustrates an example block diagram of a UE according to someembodiments.

FIG. 4 illustrates an example block diagram of a BS according to someembodiments.

FIG. 5 illustrates an example block diagram of cellular communicationcircuitry, according to some embodiments.

FIG. 6A illustrates an example of connections between an EPC network, anLTE base station (eNB), and a 5G NR base station (gNB).

FIG. 6B illustrates an example of a protocol stack for an eNB and a gNB.

FIG. 7A illustrates an example of a 5G network architecture thatincorporates both 3GPP (e.g., cellular) and non-3GPP (e.g.,non-cellular) access to the 5G CN, according to some embodiments.

FIG. 7B illustrates an example of a 5G network architecture thatincorporates both dual 3GPP (e.g., LTE and 5G NR) access and non-3GPPaccess to the 5G CN, according to some embodiments.

FIG. 8 illustrates an example of a baseband processor architecture for aUE, according to some embodiments.

FIGS. 9A and 9B illustrate examples of scenarios when DCIs end at thesame symbol, according to some embodiments.

FIGS. 10A and 10B illustrate examples of scenarios when DCIs end atdifferent symbols, according to some embodiments.

FIGS. 11, 12, 13, and 14 illustrates block diagrams of examples ofmethods for multiple transmission and reception (multi-TRP) operation,according to some embodiments.

While the features described herein may be susceptible to variousmodifications and alternative forms, specific embodiments thereof areshown by way of example in the drawings and are herein described indetail. It should be understood, however, that the drawings and detaileddescription thereto are not intended to be limiting to the particularform disclosed, but on the contrary, the intention is to cover allmodifications, equivalents and alternatives falling within the spiritand scope of the subject matter as defined by the appended claims.

DETAILED DESCRIPTION Terms

The following is a glossary of terms used in this disclosure:

Memory Medium—Any of various types of non-transitory memory devices orstorage devices. The term “memory medium” is intended to include aninstallation medium, e.g., a CD-ROM, floppy disks, or tape device; acomputer system memory or random access memory such as DRAM, DDR RAM,SRAM, EDO RAM, Rambus RAM, etc.; a non-volatile memory such as a Flash,magnetic media, e.g., a hard drive, or optical storage; registers, orother similar types of memory elements, etc. The memory medium mayinclude other types of non-transitory memory as well or combinationsthereof. In addition, the memory medium may be located in a firstcomputer system in which the programs are executed, or may be located ina second different computer system which connects to the first computersystem over a network, such as the Internet. In the latter instance, thesecond computer system may provide program instructions to the firstcomputer for execution. The term “memory medium” may include two or morememory mediums which may reside in different locations, e.g., indifferent computer systems that are connected over a network. The memorymedium may store program instructions (e.g., embodied as computerprograms) that may be executed by one or more processors.

Carrier Medium—a memory medium as described above, as well as a physicaltransmission medium, such as a bus, network, and/or other physicaltransmission medium that conveys signals such as electrical,electromagnetic, or digital signals.

Programmable Hardware Element—includes various hardware devicescomprising multiple programmable function blocks connected via aprogrammable interconnect. Examples include FPGAs (Field ProgrammableGate Arrays), PLDs (Programmable Logic Devices), FPOAs (FieldProgrammable Object Arrays), and CPLDs (Complex PLDs). The programmablefunction blocks may range from fine grained (combinatorial logic or lookup tables) to coarse grained (arithmetic logic units or processorcores). A programmable hardware element may also be referred to as“reconfigurable logic”.

Computer System—any of various types of computing or processing systems,including a personal computer system (PC), mainframe computer system,workstation, network appliance, Internet appliance, personal digitalassistant (PDA), television system, grid computing system, or otherdevice or combinations of devices. In general, the term “computersystem” can be broadly defined to encompass any device (or combinationof devices) having at least one processor that executes instructionsfrom a memory medium.

User Equipment (UE) (or “UE Device”)—any of various types of computersystems devices which are mobile or portable and which performs wirelesscommunications. Examples of UE devices include mobile telephones orsmart phones (e.g., iPhone™, Android™-based phones), portable gamingdevices (e.g., Nintendo DS™, Play Station Portable™, Gameboy Advance™,iPhone™), laptops, wearable devices (e.g. smart watch, smart glasses),PDAs, portable Internet devices, music players, data storage devices, orother handheld devices, etc. In general, the term “UE” or “UE device”can be broadly defined to encompass any electronic, computing, and/ortelecommunications device (or combination of devices) which is easilytransported by a user and capable of wireless communication.

Base Station—The term “Base Station” has the full breadth of itsordinary meaning, and at least includes a wireless communication stationinstalled at a fixed location and used to communicate as part of awireless telephone system or radio system.

Processing Element—refers to various elements or combinations ofelements that are capable of performing a function in a device, such asa user equipment or a cellular network device. Processing elements mayinclude, for example: processors and associated memory, portions orcircuits of individual processor cores, entire processor cores,processor arrays, circuits such as an ASIC (Application SpecificIntegrated Circuit), programmable hardware elements such as a fieldprogrammable gate array (FPGA), as well any of various combinations ofthe above.

Channel—a medium used to convey information from a sender (transmitter)to a receiver. It should be noted that since characteristics of the term“channel” may differ according to different wireless protocols, the term“channel” as used herein may be considered as being used in a mannerthat is consistent with the standard of the type of device withreference to which the term is used. In some standards, channel widthsmay be variable (e.g., depending on device capability, band conditions,etc.). For example, LTE may support scalable channel bandwidths from 1.4MHz to 20 MHz. In contrast, WLAN channels may be 22 MHz wide whileBluetooth channels may be 1 Mhz wide. Other protocols and standards mayinclude different definitions of channels. Furthermore, some standardsmay define and use multiple types of channels, e.g., different channelsfor uplink or downlink and/or different channels for different uses suchas data, control information, etc.

Band—The term “band” has the full breadth of its ordinary meaning, andat least includes a section of spectrum (e.g., radio frequency spectrum)in which channels are used or set aside for the same purpose.

Automatically—refers to an action or operation performed by a computersystem (e.g., software executed by the computer system) or device (e.g.,circuitry, programmable hardware elements, ASICs, etc.), without userinput directly specifying or performing the action or operation. Thusthe term “automatically” is in contrast to an operation being manuallyperformed or specified by the user, where the user provides input todirectly perform the operation. An automatic procedure may be initiatedby input provided by the user, but the subsequent actions that areperformed “automatically” are not specified by the user, i.e., are notperformed “manually”, where the user specifies each action to perform.For example, a user filling out an electronic form by selecting eachfield and providing input specifying information (e.g., by typinginformation, selecting check boxes, radio selections, etc.) is fillingout the form manually, even though the computer system must update theform in response to the user actions. The form may be automaticallyfilled out by the computer system where the computer system (e.g.,software executing on the computer system) analyzes the fields of theform and fills in the form without any user input specifying the answersto the fields. As indicated above, the user may invoke the automaticfilling of the form, but is not involved in the actual filling of theform (e.g., the user is not manually specifying answers to fields butrather they are being automatically completed). The presentspecification provides various examples of operations beingautomatically performed in response to actions the user has taken.

Approximately—refers to a value that is almost correct or exact. Forexample, approximately may refer to a value that is within 1 to 10percent of the exact (or desired) value. It should be noted, however,that the actual threshold value (or tolerance) may be applicationdependent. For example, in some embodiments, “approximately” may meanwithin 0.1% of some specified or desired value, while in various otherembodiments, the threshold may be, for example, 2%, 3%, 5%, and soforth, as desired or as required by the particular application.

Concurrent—refers to parallel execution or performance, where tasks,processes, or programs are performed in an at least partiallyoverlapping manner. For example, concurrency may be implemented using“strong” or strict parallelism, where tasks are performed (at leastpartially) in parallel on respective computational elements, or using“weak parallelism”, where the tasks are performed in an interleavedmanner, e.g., by time multiplexing of execution threads.

Various components may be described as “configured to” perform a task ortasks. In such contexts, “configured to” is a broad recitation generallymeaning “having structure that” performs the task or tasks duringoperation. As such, the component can be configured to perform the taskeven when the component is not currently performing that task (e.g., aset of electrical conductors may be configured to electrically connect amodule to another module, even when the two modules are not connected).In some contexts, “configured to” may be a broad recitation of structuregenerally meaning “having circuitry that” performs the task or tasksduring operation. As such, the component can be configured to performthe task even when the component is not currently on. In general, thecircuitry that forms the structure corresponding to “configured to” mayinclude hardware circuits.

Various components may be described as performing a task or tasks, forconvenience in the description. Such descriptions should be interpretedas including the phrase “configured to.” Reciting a component that isconfigured to perform one or more tasks is expressly intended not toinvoke 35 U.S.C. § 112(f) interpretation for that component.

FIGS. 1A and 1B—Communication Systems

FIG. 1A illustrates a simplified example wireless communication system,according to some embodiments. It is noted that the system of FIG. 1 ismerely one example of a possible system, and that features of thisdisclosure may be implemented in any of various systems, as desired.

As shown, the example wireless communication system includes a basestation 102A which communicates over a transmission medium with one ormore user devices 106A, 106B, etc., through 106N. Each of the userdevices may be referred to herein as a “user equipment” (UE). Thus, theuser devices 106 are referred to as UEs or UE devices.

The base station (BS) 102A may be a base transceiver station (BTS) orcell site (a “cellular base station”) and may include hardware thatenables wireless communication with the UEs 106A through 106N.

The communication area (or coverage area) of the base station may bereferred to as a “cell.” The base station 102A and the UEs 106 may beconfigured to communicate over the transmission medium using any ofvarious radio access technologies (RATs), also referred to as wirelesscommunication technologies, or telecommunication standards, such as GSM,UMTS (associated with, for example, WCDMA or TD-SCDMA air interfaces),LTE, LTE-Advanced (LTE-A), 5G new radio (5G NR), HSPA, 3GPP2 CDMA2000(e.g., 1×RTT, 1×EV-DO, HRPD, eHRPD), etc. Note that if the base station102A is implemented in the context of LTE, it may alternately bereferred to as an ‘eNodeB’ or ‘eNB’. Note that if the base station 102Ais implemented in the context of 5G NR, it may alternately be referredto as ‘gNodeB’ or ‘gNB’.

As shown, the base station 102A may also be equipped to communicate witha network 100 (e.g., a core network of a cellular service provider, atelecommunication network such as a public switched telephone network(PSTN), and/or the Internet, among various possibilities). Thus, thebase station 102A may facilitate communication between the user devicesand/or between the user devices and the network 100. In particular, thecellular base station 102A may provide UEs 106 with varioustelecommunication capabilities, such as voice, SMS and/or data services.

Base station 102A and other similar base stations (such as base stations102B . . . 102N) operating according to the same or a different cellularcommunication standard may thus be provided as a network of cells, whichmay provide continuous or nearly continuous overlapping service to UEs106A-N and similar devices over a geographic area via one or morecellular communication standards.

Thus, while base station 102A may act as a “serving cell” for UEs 106A-Nas illustrated in FIG. 1, each UE 106 may also be capable of receivingsignals from (and possibly within communication range of) one or moreother cells (which might be provided by base stations 102B-N and/or anyother base stations), which may be referred to as “neighboring cells”.Such cells may also be capable of facilitating communication betweenuser devices and/or between user devices and the network 100. Such cellsmay include “macro” cells, “micro” cells, “pico” cells, and/or cellswhich provide any of various other granularities of service area size.For example, base stations 102A-B illustrated in FIG. 1 might be macrocells, while base station 102N might be a micro cell. Otherconfigurations are also possible.

In some embodiments, base station 102A may be a next generation basestation, e.g., a 5G New Radio (5G NR) base station, or “gNB”. In someembodiments, a gNB may be connected to a legacy evolved packet core(EPC) network and/or to a NR core (NRC) network. In addition, a gNB cellmay include one or more transition and reception points (TRPs). Inaddition, a UE capable of operating according to 5G NR may be connectedto one or more TRPs within one or more gNBs.

Note that a UE 106 may be capable of communicating using multiplewireless communication standards. For example, the UE 106 may beconfigured to communicate using a wireless networking (e.g., Wi-Fi)and/or peer-to-peer wireless communication protocol (e.g., Bluetooth,Wi-Fi peer-to-peer, etc.) in addition to at least one cellularcommunication protocol (e.g., GSM, UMTS (associated with, for example,WCDMA or TD-SCDMA air interfaces), LTE, LTE-A, 5G NR, HSPA, 3GPP2CDMA2000 (e.g., 1×RTT, 1×EV-DO, HRPD, eHRPD), etc.). The UE 106 may alsoor alternatively be configured to communicate using one or more globalnavigational satellite systems (GNSS, e.g., GPS or GLONASS), one or moremobile television broadcasting standards (e.g., ATSC-M/H or DVB-H),and/or any other wireless communication protocol, if desired. Othercombinations of wireless communication standards (including more thantwo wireless communication standards) are also possible.

FIG. 1B illustrates user equipment 106 (e.g., one of the devices 106Athrough 106N) in communication with a base station 102 and an accesspoint 112, according to some embodiments. The UE 106 may be a devicewith both cellular communication capability and non-cellularcommunication capability (e.g., Bluetooth, Wi-Fi, and so forth) such asa mobile phone, a hand-held device, a computer or a tablet, or virtuallyany type of wireless device.

The UE 106 may include a processor that is configured to execute programinstructions stored in memory. The UE 106 may perform any of the methodembodiments described herein by executing such stored instructions.Alternatively, or in addition, the UE 106 may include a programmablehardware element such as an FPGA (field-programmable gate array) that isconfigured to perform any of the method embodiments described herein, orany portion of any of the method embodiments described herein.

The UE 106 may include one or more antennas for communicating using oneor more wireless communication protocols or technologies. In someembodiments, the UE 106 may be configured to communicate using, forexample, CDMA2000 (1×RTT/1×EV-DO/HRPD/eHRPD), LTE/LTE-Advanced, or 5G NRusing a single shared radio and/or GSM, LTE, LTE-Advanced, or 5G NRusing the single shared radio. The shared radio may couple to a singleantenna, or may couple to multiple antennas (e.g., for MIMO) forperforming wireless communications. In general, a radio may include anycombination of a baseband processor, analog RF signal processingcircuitry (e.g., including filters, mixers, oscillators, amplifiers,etc.), or digital processing circuitry (e.g., for digital modulation aswell as other digital processing). Similarly, the radio may implementone or more receive and transmit chains using the aforementionedhardware. For example, the UE 106 may share one or more parts of areceive and/or transmit chain between multiple wireless communicationtechnologies, such as those discussed above.

In some embodiments, the UE 106 may include separate transmit and/orreceive chains (e.g., including separate antennas and other radiocomponents) for each wireless communication protocol with which it isconfigured to communicate. As a further possibility, the UE 106 mayinclude one or more radios which are shared between multiple wirelesscommunication protocols, and one or more radios which are usedexclusively by a single wireless communication protocol. For example,the UE 106 might include a shared radio for communicating using eitherof LTE or 5G NR (or LTE or 1×RTTor LTE or GSM), and separate radios forcommunicating using each of Wi-Fi and Bluetooth. Other configurationsare also possible.

FIG. 2—Access Point Block Diagram

FIG. 2 illustrates an exemplary block diagram of an access point (AP)112. It is noted that the block diagram of the AP of FIG. 2 is only oneexample of a possible system. As shown, the AP 112 may includeprocessor(s) 204 which may execute program instructions for the AP 112.The processor(s) 204 may also be coupled (directly or indirectly) tomemory management unit (MMU) 240, which may be configured to receiveaddresses from the processor(s) 204 and to translate those addresses tolocations in memory (e.g., memory 260 and read only memory (ROM) 250) orto other circuits or devices.

The AP 112 may include at least one network port 270. The network port270 may be configured to couple to a wired network and provide aplurality of devices, such as UEs 106, access to the Internet. Forexample, the network port 270 (or an additional network port) may beconfigured to couple to a local network, such as a home network or anenterprise network. For example, port 270 may be an Ethernet port. Thelocal network may provide connectivity to additional networks, such asthe Internet.

The AP 112 may include at least one antenna 234, which may be configuredto operate as a wireless transceiver and may be further configured tocommunicate with UE 106 via wireless communication circuitry 230. Theantenna 234 communicates with the wireless communication circuitry 230via communication chain 232. Communication chain 232 may include one ormore receive chains, one or more transmit chains or both. The wirelesscommunication circuitry 230 may be configured to communicate via Wi-Fior WLAN, e.g., 802.11. The wireless communication circuitry 230 mayalso, or alternatively, be configured to communicate via various otherwireless communication technologies, including, but not limited to, 5GNR, Long-Term Evolution (LTE), LTE Advanced (LTE-A), Global System forMobile (GSM), Wideband Code Division Multiple Access (WCDMA), CDMA2000,etc., for example when the AP is co-located with a base station in caseof a small cell, or in other instances when it may be desirable for theAP 112 to communicate via various different wireless communicationtechnologies.

In some embodiments, as further described below, an AP 112 may beconfigured to perform methods for multi-TRP by a UE, including out oforder delivery of PDSCH, PUSCH, and/or DL ACK/NACK as further describedherein.

FIG. 3—Block Diagram of a UE

FIG. 3 illustrates an example simplified block diagram of acommunication device 106, according to some embodiments. It is notedthat the block diagram of the communication device of FIG. 3 is only oneexample of a possible communication device. According to embodiments,communication device 106 may be a user equipment (UE) device, a mobiledevice or mobile station, a wireless device or wireless station, adesktop computer or computing device, a mobile computing device (e.g., alaptop, notebook, or portable computing device), a tablet and/or acombination of devices, among other devices. As shown, the communicationdevice 106 may include a set of components 300 configured to performcore functions. For example, this set of components may be implementedas a system on chip (SOC), which may include portions for variouspurposes. Alternatively, this set of components 300 may be implementedas separate components or groups of components for the various purposes.The set of components 300 may be coupled (e.g., communicatively;directly or indirectly) to various other circuits of the communicationdevice 106.

For example, the communication device 106 may include various types ofmemory (e.g., including NAND flash 310), an input/output interface suchas connector I/F 320 (e.g., for connecting to a computer system; dock;charging station; input devices, such as a microphone, camera, keyboard;output devices, such as speakers; etc.), the display 360, which may beintegrated with or external to the communication device 106, andcellular communication circuitry 330 such as for 5G NR, LTE, GSM, etc.,and short to medium range wireless communication circuitry 329 (e.g.,Bluetooth™ and WLAN circuitry). In some embodiments, communicationdevice 106 may include wired communication circuitry (not shown), suchas a network interface card, e.g., for Ethernet.

The cellular communication circuitry 330 may couple (e.g.,communicatively; directly or indirectly) to one or more antennas, suchas antennas 335 and 336 as shown. The short to medium range wirelesscommunication circuitry 329 may also couple (e.g., communicatively;directly or indirectly) to one or more antennas, such as antennas 337and 338 as shown. Alternatively, the short to medium range wirelesscommunication circuitry 329 may couple (e.g., communicatively; directlyor indirectly) to the antennas 335 and 336 in addition to, or insteadof, coupling (e.g., communicatively; directly or indirectly) to theantennas 337 and 338. The short to medium range wireless communicationcircuitry 329 and/or cellular communication circuitry 330 may includemultiple receive chains and/or multiple transmit chains for receivingand/or transmitting multiple spatial streams, such as in amultiple-input multiple output (MIMO) configuration.

In some embodiments, as further described below, cellular communicationcircuitry 330 may include dedicated receive chains (including and/orcoupled to, e.g., communicatively; directly or indirectly. dedicatedprocessors and/or radios) for multiple RATs (e.g., a first receive chainfor LTE and a second receive chain for 5G NR). In addition, in someembodiments, cellular communication circuitry 330 may include a singletransmit chain that may be switched between radios dedicated to specificRATs. For example, a first radio may be dedicated to a first RAT, e.g.,LTE, and may be in communication with a dedicated receive chain and atransmit chain shared with an additional radio, e.g., a second radiothat may be dedicated to a second RAT, e.g., 5G NR, and may be incommunication with a dedicated receive chain and the shared transmitchain.

The communication device 106 may also include and/or be configured foruse with one or more user interface elements. The user interfaceelements may include any of various elements, such as display 360 (whichmay be a touchscreen display), a keyboard (which may be a discretekeyboard or may be implemented as part of a touchscreen display), amouse, a microphone and/or speakers, one or more cameras, one or morebuttons, and/or any of various other elements capable of providinginformation to a user and/or receiving or interpreting user input.

The communication device 106 may further include one or more smart cards345 that include SIM (Subscriber Identity Module) functionality, such asone or more UICC(s) (Universal Integrated Circuit Card(s)) cards 345.

As shown, the SOC 300 may include processor(s) 302, which may executeprogram instructions for the communication device 106 and displaycircuitry 304, which may perform graphics processing and provide displaysignals to the display 360. The processor(s) 302 may also be coupled tomemory management unit (MMU) 340, which may be configured to receiveaddresses from the processor(s) 302 and translate those addresses tolocations in memory (e.g., memory 306, read only memory (ROM) 350, NANDflash memory 310) and/or to other circuits or devices, such as thedisplay circuitry 304, short to medium range wireless communicationcircuitry 329, cellular communication circuitry 330, connector I/F 320,and/or display 360. The MMU 340 may be configured to perform memoryprotection and page table translation or set up. In some embodiments,the MMU 340 may be included as a portion of the processor(s) 302.

As noted above, the communication device 106 may be configured tocommunicate using wireless and/or wired communication circuitry. Thecommunication device 106 may be configured to perform methods formulti-TRP by a UE, including out of order delivery of PDSCH, PUSCH,and/or DL ACK/NACK as further described herein.

As described herein, the communication device 106 may include hardwareand software components for implementing the above features for acommunication device 106 to communicate a scheduling profile for powersavings to a network. The processor 302 of the communication device 106may be configured to implement part or all of the features describedherein, e.g., by executing program instructions stored on a memorymedium (e.g., a non-transitory computer-readable memory medium).Alternatively (or in addition), processor 302 may be configured as aprogrammable hardware element, such as an FPGA (Field Programmable GateArray), or as an ASIC (Application Specific Integrated Circuit).Alternatively (or in addition) the processor 302 of the communicationdevice 106, in conjunction with one or more of the other components 300,304, 306, 310, 320, 329, 330, 340, 345, 350, 360 may be configured toimplement part or all of the features described herein.

In addition, as described herein, processor 302 may include one or moreprocessing elements. Thus, processor 302 may include one or moreintegrated circuits (ICs) that are configured to perform the functionsof processor 302. In addition, each integrated circuit may includecircuitry (e.g., first circuitry, second circuitry, etc.) configured toperform the functions of processor(s) 302.

Further, as described herein, cellular communication circuitry 330 andshort to medium range wireless communication circuitry 329 may eachinclude one or more processing elements. In other words, one or moreprocessing elements may be included in cellular communication circuitry330 and, similarly, one or more processing elements may be included inshort to medium range wireless communication circuitry 329. Thus,cellular communication circuitry 330 may include one or more integratedcircuits (ICs) that are configured to perform the functions of cellularcommunication circuitry 330. In addition, each integrated circuit mayinclude circuitry (e.g., first circuitry, second circuitry, etc.)configured to perform the functions of cellular communication circuitry330. Similarly, the short to medium range wireless communicationcircuitry 329 may include one or more ICs that are configured to performthe functions of short to medium range wireless communication circuitry329. In addition, each integrated circuit may include circuitry (e.g.,first circuitry, second circuitry, etc.) configured to perform thefunctions of short to medium range wireless communication circuitry 329.

FIG. 4—Block Diagram of a Base Station

FIG. 4 illustrates an example block diagram of a base station 102,according to some embodiments. It is noted that the base station of FIG.4 is merely one example of a possible base station. As shown, the basestation 102 may include processor(s) 404 which may execute programinstructions for the base station 102. The processor(s) 404 may also becoupled to memory management unit (MMU) 440, which may be configured toreceive addresses from the processor(s) 404 and translate thoseaddresses to locations in memory (e.g., memory 460 and read only memory(ROM) 450) or to other circuits or devices.

The base station 102 may include at least one network port 470. Thenetwork port 470 may be configured to couple to a telephone network andprovide a plurality of devices, such as UE devices 106, access to thetelephone network as described above in FIGS. 1 and 2.

The network port 470 (or an additional network port) may also oralternatively be configured to couple to a cellular network, e.g., acore network of a cellular service provider. The core network mayprovide mobility related services and/or other services to a pluralityof devices, such as UE devices 106. In some cases, the network port 470may couple to a telephone network via the core network, and/or the corenetwork may provide a telephone network (e.g., among other UE devicesserviced by the cellular service provider).

In some embodiments, base station 102 may be a next generation basestation, e.g., a 5G New Radio (5G NR) base station, or “gNB”. In suchembodiments, base station 102 may be connected to a legacy evolvedpacket core (EPC) network and/or to a NR core (NRC) network. Inaddition, base station 102 may be considered a 5G NR cell and mayinclude one or more transition and reception points (TRPs). In addition,a UE capable of operating according to 5G NR may be connected to one ormore TRPs within one or more gNBs.

The base station 102 may include at least one antenna 434, and possiblymultiple antennas. The at least one antenna 434 may be configured tooperate as a wireless transceiver and may be further configured tocommunicate with UE devices 106 via radio 430. The antenna 434communicates with the radio 430 via communication chain 432.Communication chain 432 may be a receive chain, a transmit chain orboth. The radio 430 may be configured to communicate via variouswireless communication standards, including, but not limited to, 5G NR,LTE, LTE-A, GSM, UMTS, CDMA2000, Wi-Fi, etc.

The base station 102 may be configured to communicate wirelessly usingmultiple wireless communication standards. In some instances, the basestation 102 may include multiple radios, which may enable the basestation 102 to communicate according to multiple wireless communicationtechnologies. For example, as one possibility, the base station 102 mayinclude an LTE radio for performing communication according to LTE aswell as a 5G NR radio for performing communication according to 5G NR.In such a case, the base station 102 may be capable of operating as bothan LTE base station and a 5G NR base station. As another possibility,the base station 102 may include a multi-mode radio which is capable ofperforming communications according to any of multiple wirelesscommunication technologies (e.g., 5G NR and Wi-Fi, LTE and Wi-Fi, LTEand UMTS, LTE and CDMA2000, UMTS and GSM, etc.).

As described further subsequently herein, the BS 102 may includehardware and software components for implementing or supportingimplementation of features described herein. The processor 404 of thebase station 102 may be configured to implement or supportimplementation of part or all of the methods described herein, e.g., byexecuting program instructions stored on a memory medium (e.g., anon-transitory computer-readable memory medium). Alternatively, theprocessor 404 may be configured as a programmable hardware element, suchas an FPGA (Field Programmable Gate Array), or as an ASIC (ApplicationSpecific Integrated Circuit), or a combination thereof. Alternatively(or in addition) the processor 404 of the BS 102, in conjunction withone or more of the other components 430, 432, 434, 440, 450, 460, 470may be configured to implement or support implementation of part or allof the features described herein.

In addition, as described herein, processor(s) 404 may be comprised ofone or more processing elements. In other words, one or more processingelements may be included in processor(s) 404. Thus, processor(s) 404 mayinclude one or more integrated circuits (ICs) that are configured toperform the functions of processor(s) 404. In addition, each integratedcircuit may include circuitry (e.g., first circuitry, second circuitry,etc.) configured to perform the functions of processor(s) 404.

Further, as described herein, radio 430 may be comprised of one or moreprocessing elements. In other words, one or more processing elements maybe included in radio 430. Thus, radio 430 may include one or moreintegrated circuits (ICs) that are configured to perform the functionsof radio 430. In addition, each integrated circuit may include circuitry(e.g., first circuitry, second circuitry, etc.) configured to performthe functions of radio 430.

FIG. 5: Block Diagram of Cellular Communication Circuitry

FIG. 5 illustrates an example simplified block diagram of cellularcommunication circuitry, according to some embodiments. It is noted thatthe block diagram of the cellular communication circuitry of FIG. 5 isonly one example of a possible cellular communication circuit. Accordingto embodiments, cellular communication circuitry 330 may be included ina communication device, such as communication device 106 describedabove. As noted above, communication device 106 may be a user equipment(UE) device, a mobile device or mobile station, a wireless device orwireless station, a desktop computer or computing device, a mobilecomputing device (e.g., a laptop, notebook, or portable computingdevice), a tablet and/or a combination of devices, among other devices.

The cellular communication circuitry 330 may couple (e.g.,communicatively; directly or indirectly) to one or more antennas, suchas antennas 335 a-b and 336 as shown (in FIG. 3). In some embodiments,cellular communication circuitry 330 may include dedicated receivechains (including and/or coupled to, e.g., communicatively; directly orindirectly. dedicated processors and/or radios) for multiple RATs (e.g.,a first receive chain for LTE and a second receive chain for 5G NR). Forexample, as shown in FIG. 5, cellular communication circuitry 330 mayinclude a modem 510 and a modem 520. Modem 510 may be configured forcommunications according to a first RAT, e.g., such as LTE or LTE-A, andmodem 520 may be configured for communications according to a secondRAT, e.g., such as 5G NR.

As shown, modem 510 may include one or more processors 512 and a memory516 in communication with processors 512. Modem 510 may be incommunication with a radio frequency (RF) front end 530. RF front end530 may include circuitry for transmitting and receiving radio signals.For example, RF front end 530 may include receive circuitry (RX) 532 andtransmit circuitry (TX) 534. In some embodiments, receive circuitry 532may be in communication with downlink (DL) front end 550, which mayinclude circuitry for receiving radio signals via antenna 335 a.

Similarly, modem 520 may include one or more processors 522 and a memory526 in communication with processors 522. Modem 520 may be incommunication with an RF front end 540. RF front end 540 may includecircuitry for transmitting and receiving radio signals. For example, RFfront end 540 may include receive circuitry 542 and transmit circuitry544. In some embodiments, receive circuitry 542 may be in communicationwith DL front end 560, which may include circuitry for receiving radiosignals via antenna 335 b.

In some embodiments, a switch 570 may couple transmit circuitry 534 touplink (UL) front end 572. In addition, switch 570 may couple transmitcircuitry 544 to UL front end 572. UL front end 572 may includecircuitry for transmitting radio signals via antenna 336. Thus, whencellular communication circuitry 330 receives instructions to transmitaccording to the first RAT (e.g., as supported via modem 510), switch570 may be switched to a first state that allows modem 510 to transmitsignals according to the first RAT (e.g., via a transmit chain thatincludes transmit circuitry 534 and UL front end 572). Similarly, whencellular communication circuitry 330 receives instructions to transmitaccording to the second RAT (e.g., as supported via modem 520), switch570 may be switched to a second state that allows modem 520 to transmitsignals according to the second RAT (e.g., via a transmit chain thatincludes transmit circuitry 544 and UL front end 572).

In some embodiments, the cellular communication circuitry 330 may beconfigured to perform methods for multi-TRP by a UE, including out oforder delivery of PDSCH, PUSCH, and/or DL ACK/NACK as further describedherein.

As described herein, the modem 510 may include hardware and softwarecomponents for implementing the above features or for time divisionmultiplexing UL data for NSA NR operations, as well as the various othertechniques described herein. The processors 512 may be configured toimplement part or all of the features described herein, e.g., byexecuting program instructions stored on a memory medium (e.g., anon-transitory computer-readable memory medium). Alternatively (or inaddition), processor 512 may be configured as a programmable hardwareelement, such as an FPGA (Field Programmable Gate Array), or as an ASIC(Application Specific Integrated Circuit). Alternatively (or inaddition) the processor 512, in conjunction with one or more of theother components 530, 532, 534, 550, 570, 572, 335 and 336 may beconfigured to implement part or all of the features described herein.

In addition, as described herein, processors 512 may include one or moreprocessing elements. Thus, processors 512 may include one or moreintegrated circuits (ICs) that are configured to perform the functionsof processors 512. In addition, each integrated circuit may includecircuitry (e.g., first circuitry, second circuitry, etc.) configured toperform the functions of processors 512.

As described herein, the modem 520 may include hardware and softwarecomponents for implementing the above features for communicating ascheduling profile for power savings to a network, as well as thevarious other techniques described herein. The processors 522 may beconfigured to implement part or all of the features described herein,e.g., by executing program instructions stored on a memory medium (e.g.,a non-transitory computer-readable memory medium). Alternatively (or inaddition), processor 522 may be configured as a programmable hardwareelement, such as an FPGA (Field Programmable Gate Array), or as an ASIC(Application Specific Integrated Circuit). Alternatively (or inaddition) the processor 522, in conjunction with one or more of theother components 540, 542, 544, 550, 570, 572, 335 and 336 may beconfigured to implement part or all of the features described herein.

In addition, as described herein, processors 522 may include one or moreprocessing elements. Thus, processors 522 may include one or moreintegrated circuits (ICs) that are configured to perform the functionsof processors 522. In addition, each integrated circuit may includecircuitry (e.g., first circuitry, second circuitry, etc.) configured toperform the functions of processors 522.

5G NR Architecture with LTE

In some implementations, fifth generation (5G) wireless communicationwill initially be deployed concurrently with current wirelesscommunication standards (e.g., LTE). For example, dual connectivitybetween LTE and 5G new radio (5G NR or NR) has been specified as part ofthe initial deployment of NR. Thus, as illustrated in FIGS. 6A-B,evolved packet core (EPC) network 600 may continue to communicate withcurrent LTE base stations (e.g., eNB 602). In addition, eNB 602 may bein communication with a 5G NR base station (e.g., gNB 604) and may passdata between the EPC network 600 and gNB 604. Thus, EPC network 600 maybe used (or reused) and gNB 604 may serve as extra capacity for UEs,e.g., for providing increased downlink throughput to UEs. In otherwords, LTE may be used for control plane signaling and NR may be usedfor user plane signaling. Thus, LTE may be used to establish connectionsto the network and NR may be used for data services.

FIG. 6B illustrates a proposed protocol stack for eNB 602 and gNB 604.As shown, eNB 602 may include a medium access control (MAC) layer 632that interfaces with radio link control (RLC) layers 622 a-b. RLC layer622 a may also interface with packet data convergence protocol (PDCP)layer 612 a and RLC layer 622 b may interface with PDCP layer 612 b.Similar to dual connectivity as specified in LTE-Advanced Release 12,PDCP layer 612 a may interface via a master cell group (MCG) bearer withEPC network 600 whereas PDCP layer 612 b may interface via a splitbearer with EPC network 600.

Additionally, as shown, gNB 604 may include a MAC layer 634 thatinterfaces with RLC layers 624 a-b. RLC layer 624 a may interface withPDCP layer 612 b of eNB 602 via an X2 interface for information exchangeand/or coordination (e.g., scheduling of a UE) between eNB 602 and gNB604. In addition, RLC layer 624 b may interface with PDCP layer 614.Similar to dual connectivity as specified in LTE-Advanced Release 12,PDCP layer 614 may interface with EPC network 600 via a secondary cellgroup (SCG) bearer. Thus, eNB 602 may be considered a master node (MeNB)while gNB 604 may be considered a secondary node (SgNB). In somescenarios, a UE may be required to maintain a connection to both an MeNBand a SgNB. In such scenarios, the MeNB may be used to maintain a radioresource control (RRC) connection to an EPC while the SgNB may be usedfor capacity (e.g., additional downlink and/or uplink throughput).

5G Core Network Architecture—Interworking with Wi-Fi

In some embodiments, the 5G core network (CN) may be accessed via (orthrough) a cellular connection/interface (e.g., via a 3GPP communicationarchitecture/protocol) and a non-cellular connection/interface (e.g., anon-3GPP access architecture/protocol such as Wi-Fi connection). FIG. 7Aillustrates an example of a 5G network architecture that incorporatesboth 3GPP (e.g., cellular) and non-3GPP (e.g., non-cellular) access tothe 5G CN, according to some embodiments. As shown, a user equipmentdevice (e.g., such as UE 106) may access the 5G CN through both a radioaccess network (RAN, e.g., such as gNB or base station 604) and anaccess point, such as AP 112. The AP 112 may include a connection to theInternet 700 as well as a connection to a non-3GPP inter-workingfunction (N3IWF) 702 network entity. The N3IWF may include a connectionto a core access and mobility management function (AMF) 704 of the 5GCN. The AMF 704 may include an instance of a 5G mobility management (5GMM) function associated with the UE 106. In addition, the RAN (e.g., gNB604) may also have a connection to the AMF 704. Thus, the 5G CN maysupport unified authentication over both connections as well as allowsimultaneous registration for UE 106 access via both gNB 604 and AP 112.As shown, the AMF 704 may include one or more functional entitiesassociated with the 5G CN (e.g., network slice selection function (NSSF)720, short message service function (SMSF) 722, application function(AF) 724, unified data management (UDM) 726, policy control function(PCF) 728, and/or authentication server function (AUSF) 730). Note thatthese functional entities may also be supported by a session managementfunction (SMF) 706 a and an SMF 706 b of the 5G CN. The AMF 706 may beconnected to (or in communication with) the SMF 706 a. Further, the gNB604 may in communication with (or connected to) a user plane function(UPF) 708 a that may also be communication with the SMF 706 a.Similarly, the N3IWF 702 may be communicating with a UPF 708 b that mayalso be communicating with the SMF 706 b. Both UPFs may be communicatingwith the data network (e.g., DN 710 a and 710 b) and/or the Internet 700and IMS core network 710.

FIG. 7B illustrates an example of a 5G network architecture thatincorporates both dual 3GPP (e.g., LTE and 5G NR) access and non-3GPPaccess to the 5G CN, according to some embodiments. As shown, a userequipment device (e.g., such as UE 106) may access the 5G CN throughboth a radio access network (RAN, e.g., such as gNB or base station 604or eNB or base station 602) and an access point, such as AP 112. The AP112 may include a connection to the Internet 700 as well as a connectionto the N3IWF 702 network entity. The N3IWF may include a connection tothe AMF 704 of the 5G CN. The AMF 704 may include an instance of the 5GMM function associated with the UE 106. In addition, the RAN (e.g., gNB604) may also have a connection to the AMF 704. Thus, the 5G CN maysupport unified authentication over both connections as well as allowsimultaneous registration for UE 106 access via both gNB 604 and AP 112.In addition, the 5G CN may support dual-registration of the UE on both alegacy network (e.g., LTE via base station 602) and a 5G network (e.g.,via base station 604). As shown, the base station 602 may haveconnections to a mobility management entity (MME) 742 and a servinggateway (SGW) 744. The MME 742 may have connections to both the SGW 744and the AMF 704. In addition, the SGW 744 may have connections to boththe SMF 706 a and the UPF 708 a. As shown, the AMF 704 may include oneor more functional entities associated with the 5G CN (e.g., NSSF 720,SMSF 722, AF 724, UDM 726, PCF 728, and/or AUSF 730). Note that UDM 726may also include a home subscriber server (HSS) function and the PCF mayalso include a policy and charging rules function (PCRF). Note furtherthat these functional entities may also be supported by the SMF 706 aand the SMF 706 b of the 5G CN. The AMF 706 may be connected to (or incommunication with) the SMF 706 a. Further, the gNB 604 may incommunication with (or connected to) the UPF 708 a that may also becommunication with the SMF 706 a. Similarly, the N3IWF 702 may becommunicating with a UPF 708 b that may also be communicating with theSMF 706 b. Both UPFs may be communicating with the data network (e.g.,DN 710 a and 710 b) and/or the Internet 700 and IMS core network 710.

Note that in various embodiments, one or more of the above describednetwork entities may be configured for multi-TRP by a UE, including outof order delivery of PDSCH, PUSCH, and/or DL ACK/NACK, e.g., as furtherdescribed herein.

FIG. 8 illustrates an example of a baseband processor architecture for aUE (e.g., such as UE 106), according to some embodiments. The basebandprocessor architecture 800 described in FIG. 8 may be implemented on oneor more radios (e.g., radios 329 and/or 330 described above) or modems(e.g., modems 510 and/or 520) as described above. As shown, thenon-access stratum (NAS) 810 may include a 5G NAS 820 and a legacy NAS850. The legacy NAS 850 may include a communication connection with alegacy access stratum (AS) 870. The 5G NAS 820 may include communicationconnections with both a 5G AS 840 and a non-3GPP AS 830 and Wi-Fi AS832. The 5G NAS 820 may include functional entities associated with bothaccess stratums. Thus, the 5G NAS 820 may include multiple 5G MMentities 826 and 828 and 5G session management (SM) entities 822 and824. The legacy NAS 850 may include functional entities such as shortmessage service (SMS) entity 852, evolved packet system (EPS) sessionmanagement (ESM) entity 854, session management (SM) entity 856, EPSmobility management (EMM) entity 858, and mobility management (MM)/GPRSmobility management (GMM) entity 860. In addition, the legacy AS 870 mayinclude functional entities such as LTE AS 872, UMTS AS 874, and/orGSM/GPRS AS 876.

Thus, the baseband processor architecture 800 allows for a common 5G-NASfor both 5G cellular and non-cellular (e.g., non-3GPP access). Note thatas shown, the 5G MM may maintain individual connection management andregistration management state machines for each connection.Additionally, a device (e.g., UE 106) may register to a single PLMN(e.g., 5G CN) using 5G cellular access as well as non-cellular access.Further, it may be possible for the device to be in a connected state inone access and an idle state in another access and vice versa. Finally,there may be common 5G-MM procedures (e.g., registration,de-registration, identification, authentication, as so forth) for bothaccesses.

Note that in various embodiments, one or more of the above describedfunctional entities of the 5G NAS and/or 5G AS may be configured toperform methods for multi-TRP by a UE, including out of order deliveryof PDSCH, PUSCH, and/or DL ACK/NACK, e.g., as further described herein.

Multi-TRP

In current implementations, out of order delivery of a physical downlinkshared channel (PDSCH), a physical uplink shared channel (PUSCH), and adownlink (DL) acknowledgment/negative acknowledgement (ACK/NACK) areprohibited. In particular, with regards to PDSCH, currentimplementations of the 3GPP standard (e.g., such as Release 15) statethat “[f]or any two HARQ process IDs in a given scheduled cell, if theUE is scheduled to start receiving a first PDSCH starting in symbol j bya PDCCH ending in symbol i, the UE is not expected to be scheduled toreceive a PDSCH starting earlier than the end of the first PDSCH with aPDCCH that ends later than symbol i. Similarly, with regards to PUSCH,current implementations of the 3GPP standard (e.g., such as Release 15)state that “[f]or any two HARQ process IDs in a given scheduled cell, ifthe UE is scheduled to start a first PUSCH transmission starting insymbol j by a PDCCH ending in symbol i, the UE is not expected to bescheduled to transmit a PUSCH starting earlier than the first PUSCH witha PDCCH that ends later than symbol i. Additionally, with regards to DLACK/NACK, current implementations of the 3GPP standard (e.g., such asRelease 15) state that “[i]n a give scheduled cell, the UE is notexpected to receive a first PDSCH in slot i, with the corresponding HARQACK assigned to be transmitted in slot j, and a second PDSCH startinglater than the first PDSCH with its corresponding HARQ-ACK assigned tobe transmitted before slot j.

However, current implementations of MIMO (e.g., Release 15) support outof order delivery, but it is an optional feature for the UE.Additionally, multi-DCI design of MIMO allows two DCI to end at the samesymbol. In other words, there may be multiple control resource set(CORESET) pools (e.g., CORESETPool).

Embodiments described herein provide mechanisms to allow a UE to decodemultiple PDSCHs when multiple DCIs are configured. For example, FIG. 9Aillustrates a scenario in which multiple DCIs end at the same symbol andFIG. 9B illustrates various example relationships of PDSCHs scheduledbased on the DCIs of FIG. 9A. As illustrated by FIG. 9A, DCI 910 ofCORESETPool 0 and DCI 920 of CORESETPool 1 may end at the same symbol.As illustrated by FIG. 9B, such a scenario may lead to various relative(in time) positions of PDSCHs associated with the DCIs (e.g. PDSCH 912associated with DCI 910 and PDSCH 922 associated with DCI 920). Forexample, as illustrated by 930, PDSCH 922 may start at the end of PDSCH912 and the PDSCHs may not overlap. Alternatively, as illustrated by932, PDSCH 912 and PDSCH 922 may start and end at the same symbols andmay fully overlap. Further, as illustrated by 934, PDSCH 912 may startprior to the start of PDSCH 922, but the PDSCHs may at least partiallyoverlap. Similarly, as illustrated by 936, PDSCH 922 may start prior tothe start of PDSCH 912, but the PDSCHs may at least partially overlap.Finally, as illustrated by 938, PDSCH 912 may start at the end of PDSCH922 and the PDSCHs may not overlap.

In some embodiments, a UE may support multi-TRP operation, but may notsupport out of order PDSCH when 2 DCIs end at the same symbol, relyingon a CORESETPool index to determine ordering of the PDSCHs. In someembodiments, for any two HARQ process IDs in a given scheduled cell,when the UE is scheduled to start receiving a first PDSCH starting insymbol j by a PDCCH from a CORESETPool with index 0 ending in symbol i,the UE may not be expected to be scheduled to receive a PDSCH startingearlier than the end of the first PDSCH with a PDCCH that ends also insymbol j from different CORESETPool, thus such embodiments may onlysupport the example illustrated by 930 and may not support the examplesillustrated by 932, 934, 936, and/or 938. In other words, suchembodiments may only support in order delivery of the PDSCHs, whereorder may be determined by CORESETPool index. In some embodiments, forany two HARQ process IDs in a given scheduled cell, when the UE isscheduled to start receiving a first PDSCH starting in symbol j by aPDCCH from CORESETPool with index 0 ending in symbol i, the UE may notbe expected to be scheduled to receive a PDSCH starting earlier than thefirst symbol of the first PDSCH with a PDCCH that ends also in symbol jfrom different CORESETPool, thus such embodiments may only support theexamples illustrated by 930, 932, and 934 and may not support theexamples illustrated by 936 and/or 938. In other words, such embodimentsmay only support delivery of the PDSCHs when a second PDSCH starts noearlier than a start of a first PDSCH, where order may be determined byCORESETPool index. In some embodiments, for any two HARQ process IDs ina given scheduled cell, when the UE is scheduled to start receiving afirst PDSCH starting in symbol j by a PDCCH from CORESETPool with index0 ending in symbol i, the UE may not be expected to be scheduled toreceive a PDSCH ending earlier than the first symbol of the first PDSCHwith a PDCCH that ends also in symbol j from different CORESETPools,thus such embodiments may only support the examples illustrated by 930,932, 934 and 936 and may not support the example illustrated by 938. Inother words, such embodiments may only support delivery of the PDSCHswhen a second PDSCH does not end prior to a start of a first PDSCH,where order may be determined by CORESETPool index.

In some embodiments, a UE may support multi-TRP operation, but may notsupport out of order PDSCH when 2 DCI ends at the same symbol, but notrelying on a CORESETPool index to determine ordering of the PDSCHs. Insome embodiments, for any two HARQ process IDs in a given scheduledcell, when the UE is scheduled to start receiving a first PDSCH startingin symbol j by a PDCCH ending in symbol i, the UE may not be expected tobe scheduled to receive a PDSCH with any time relation to the firstPDSCH with a PDCCH that ends also in symbol j from differentCORESETPools, thus such embodiments may support the examples illustratedby 930, 932, 934, 936 and 938. In other words, such embodiments maysupport any order of delivery of the PDSCHs. In some embodiments, forany two HARQ process IDs in a given scheduled cell, when the UE isscheduled to start receiving a first PDSCH starting in symbol j by aPDCCH ending in symbol i, the UE may not be expected to be scheduled toreceive a PDSCH that overlaps with the first PDSCH with a PDCCH thatends also in symbol j from different CORESETPools, thus such embodimentsmay only support the examples illustrated by 930 and 938 and may notsupport the examples illustrated by 932, 934, and 936. In other words,such embodiments may only support delivery of the PDSCHs when deliveryof the PDSCHs does not overlap. In some embodiments, for any two HARQprocess IDs in a given scheduled cell, when the UE is scheduled to startreceiving a first PDSCH starting in symbol j by a PDCCH ending in symboli, the UE may not be expected to be scheduled to receive a PDSCH thatdoes not overlap with the first PDSCH with a PDCCH that ends also insymbol j from different CORESETPools, thus such embodiments may onlysupport the examples illustrated by 932, 934 and 936 and may not supportthe examples illustrated by 930 and 938. In other words, suchembodiments may only support delivery of the PDSCHs when delivery of thePDSCHs at least partially overlap.

FIG. 10A illustrates a scenario in which multiple DCIs end at adifferent symbol and FIG. 10B illustrates various example relationshipsof PDSCHs scheduled based on the DCIs of FIG. 10A. As illustrated byFIG. 10A, DCI 1010 of CORESETPool 0 and DCI 1020 of CORESETPool 1 mayend at different symbols. As illustrated by FIG. 10B, such a scenariomay lead to various relative (in time) positions of PDSCHs associatedwith the DCIs (e.g. PDSCH 1012 associated with DCI 1010 and PDSCH 1022associated with DCI 1020). For example, as illustrated by 1030, PDSCH1022 may start at the end of PDSCH 1012 and the PDSCHs may not overlap.Alternatively, as illustrated by 1032, PDSCH 1012 and PDSCH 1022 maystart and end at the same symbols and may fully overlap. Further, asillustrated by 1034, PDSCH 1012 may start prior to the start of PDSCH1022, but the PDSCHs may at least partially overlap. Similarly, asillustrated by 1036, PDSCH 1022 may start prior to the start of PDSCH1012, but the PDSCHs may at least partially overlap.

In some embodiments, a UE may support multi-TRP operation, but may notsupport out of order PDSCH when 2 DCI ends at different symbols. In someembodiments, for any two HARQ process IDs in a given scheduled cell,when the UE is scheduled to start receiving a first PDSCH starting insymbol j by a PDCCH ending in symbol i, the UE may not be expected to bescheduled to receive a PDSCH starting earlier than the end of the firstPDSCH with a PDCCH that ends later than symbol i from differentCORESETPool, thus such embodiments may only support the exampleillustrated by 1030 and may not support the examples illustrated by1032, 1034, and/or 1036. In other words, such embodiments may onlysupport in order delivery of the PDSCHs, where order may be determinedby CORESETPool index. In some embodiments, for any two HARQ process IDsin a given scheduled cell, when the UE is scheduled to start receiving afirst PDSCH starting in symbol j by a PDCCH ending in symbol i, the UEmay not be expected to be scheduled to receive a PDSCH starting earlierthan the first symbol of the first PDSCH with a PDCCH that ends laterthan symbol i from different CORESETPool, thus such embodiments may onlysupport the examples illustrated by 1030, 1032, and 1034 and may notsupport the example illustrated 1036. In other words, such embodimentsmay only support delivery of the PDSCHs when a second PDSCH starts noearlier than a start of a first PDSCH.

In some embodiments, the principles described herein associated with thePDSCH may be used for PUSCH, except, overlapping PUSCH may be allowed,e.g., when a DCI ends at the same symbol utilizing CORESETPool, astarting symbol of PUSCH from CORESETPool 1 has to be later than theending symbol of PUSCH from CORESETPool 0. Similarly, when a DCI ends atthe same symbol and CORSETPool is not utilized, any timing relationexcept that 2 PUSCH cannot overlap may be used. In some embodiments,when DCIs end at different symbols, a starting symbol of a PUSCHscheduled by a later DCI has to be later than an ending symbol of PUSCHscheduled by an earlier DCI.

In some embodiments, the principles described herein associated with thePDSCH may be used for DL ACK/NACK. In some embodiments, in the sameslot, for PDSCH scheduled by different CORESETPools, their ACK/NACK canhave any time relationship. In some embodiments, a CORESETPool otherthan index 0 may not schedule an ACK/NACK earlier than a slot scheduledby CORESETPool 0 for ACK/NACK.

In some embodiments, for each monitoring occasion, up to 2 CORSETPoolsmay be configured. Thus, a UE may double its downlink decoding subjectto UE capability. For example, for feature group 3-1 (e.g., UE onlysupports single monitoring occasion for each slot):

for frequency division duplexing (FDD): one unicast DL and one unicastUL per slot per scheduled component carrier (CC) per CORESETPool;

for time division duplexing (TDD): one unicast DL and two unicast UL perslot per scheduled CC per CORESETPool.

Similarly, for feature group 3-5(b) (e.g., UE supports multiplemonitoring occasion each slot):

for FDD: one unicast DL and one unicast UL per CC per set of monitoringoccasions per CORESETPool;

for TDD: one unicast DL and two unicast UL per CC per set of monitoringoccasions per CORESETPool;

for TDD: two unicast DL and one unicast UL per CC per set of monitoringoccasions per CORESETPool.

In some embodiments, a UE may indicate when it supports single DCImulti-TRP operation mode 1, 2a, 2b, 3, 4 independently. In someembodiments, when the UE indicates it does not support a mode, but thenetwork dynamically configures it, it may be considered an error casewith unexpected UE behavior. In such embodiments, default behaviorand/or fall back mode may be allowed, e.g.:

Mode 1: only one TCI state is used;

Mode 2a: only one TCI state is used, drop the PRB belongs to the secondTRP;

Mode 2b: only one TCI state is used, drop the PRB belongs to the secondTRP;

Mode 3: only one TCI state is used, drop all PDSCH except the first one;and/or

Mode 4: only one TCI state is used, drop all PDSCH except the first one.

In some embodiments, for a multi-TRP multi-DCI based ultra reliable lowlatency communication (URLLC) scheme, the UE may receive 2 PDSCHs withthe same HARQ process ID overlapping in time. In some embodiments, forany HARQ process ID(s) in a given scheduled cell, the UE may bescheduled to receive 2 PDSCHs that overlap in time, e.g., when eachPDSCH is scheduled by a DCI from different CORESETPool.

In some embodiments, for a multi-TRP multi-DCI based URLLC scheme, theUE may be scheduled to receive PDSCHs with the same HARQ process IDsbefore the ACK/NACK. In some embodiments, the UE may be scheduled toreceive another PDSCH for a given HARQ process ID before the end of theexpected transmission of HARQ-ACK for that HARQ process ID if (when) thePDSCH is scheduled by a DCI from another CORESETPool or cells inmulti-TRP operation.

In some embodiments, a UE may indicate that it does not support R=2, forN3 less than or equal to 19, where N3 is a number of pre-coding matrixindicator (PMI) sub-bands and where R (either 1 or 2) is a number of PMIsub-bands per channel quality indicator (CQI) sub-band. In someembodiments, the UE may support R=2 for N3 less than or equal to 19under the conditions of:

CSI reporting with R=2 and N3 less than or equal to 19 accounts for 2CPU (channel state information (CSI) processing unit); and

for aperiodic (AP) CSI reporting, Z and Z′ timing requirements may befurther relaxed.

FIGS. 11, 12, 13, and 14 illustrate block diagrams of examples ofmethods for multiple transmission and reception (multi-TRP) operation,according to some embodiments. The methods shown in FIGS. 11, 12, and 13may be used in conjunction with any of the systems, methods, or devicesshown in the Figures, among other devices. In various embodiments, someof the method elements shown may be performed concurrently, in adifferent order than shown, or may be omitted. Additional methodelements may also be performed as desired.

Turning to FIG. 11, illustrated is a block diagram of an example ofmulti-TRP operation for reception, according to some embodiments. At1102, a UE, such as UE 106 may receive, from a base station, such asbase station 102, a configuration that may include multiple controlresource set (CORESET) pools. In some embodiments, each CORESET pool maybe associated with an index value, e.g., a CORESETPool index. In someembodiments, for each CORESET pool of the multiple CORESET pools, the UEmay:

for frequency division duplexing, monitor one unicast downlinktransmission and one unicast uplink transmission per slot per scheduledcomponent carrier per CORESET pool; and/or

for time division duplexing, monitor one unicast downlink transmissionand two unicast uplink transmissions per slot per scheduled componentcarrier per CORESET pool. In some embodiments, for each CORESET pool ofthe multiple CORESET pools, the UE may:

for frequency division duplexing, monitor one unicast downlinktransmission and one unicast uplink transmission per component carrierset of monitoring occasions per CORESET pool;

for time division duplexing, monitor one unicast downlink transmissionand two unicast uplink transmissions per component carrier set ofmonitoring occasions per CORESET pool; and/or

for time division duplexing, monitor two unicast downlink transmissionsand one unicast uplink transmission per component carrier set ofmonitoring occasions per CORESET pool.

At 1104, the UE may receive, from the base station, multiple downlinkcontrol indexes (DCIs). In some embodiments, each DCI may be associatedwith a CORESET pool, e.g., with a CORESET pool index value.

At 1106, the UE may determine that at least two DCIs of the multipleDCIs end at a common symbol. In other words, the UE may determine thatmore than one DCI ends at the same symbol.

At 1108, the UE may determine, based on a predetermined rule, when theUE may be scheduled to receive physical downlink control channels(PDSCHs) from CORESETs associated with the at least two DCIs. In otherwords, the UE may determine a possible relationship between the PDSCHsassociated with the at least 2 DCIs based on the predetermined rule,e.g., an earliest possible starting/ending symbol of one PDSCH relativeto another PDSCH. In some embodiments, the predetermined rule mayinclude at least one of no overlap between PDSCHs (e.g., a startingsymbol of one PDSCH does not occur until after an ending symbol ofanother PDSCH) or at least partial overlap between PDSCHs (e.g., astarting symbol of one PDSCH occurs prior to an ending symbol of anotherPDSCH).

In some embodiments, the predetermined rule may be based on the indexvalue, e.g. the CORESETPool index. For example, when the predeterminedrule is based on the index value, the predetermined rule may include atleast one of:

when the UE is scheduled to start receiving a first PDSCH starting insymbol j by a physical downlink control channel (PDCCH) from a firstCORESET pool with an index value of 0 and ending in symbol i, the UE maynot be expected to be scheduled to receive a second PDSCH startingearlier than the end of the first PDSCH with a PDCCH that ends also insymbol j from a CORESET pool with non-zero index value;

when the UE is scheduled to start receiving a first PDSCH starting insymbol j by a PDCCH from a first CORESET pool with an index value of 0and ending in symbol i, the UE may not be expected to be scheduled toreceive a second PDSCH starting earlier than the first symbol of thefirst PDSCH with a PDCCH that ends also in symbol j from a CORESET poolwith non-zero index value; and/or

when the UE is scheduled to start receiving a first PDSCH starting insymbol j by a PDCCH from a first CORESET pool with an index value 0ending in symbol i, the UE may not be expected to be scheduled toreceive a second PDSCH ending earlier than the first symbol of the firstPDSCH with a PDCCH that ends also in symbol j from a CORESET pool withnon-zero index value.

In some embodiments, the predetermined rule may be based on a timingrelationship between the PDSCHs. In such embodiments, the predeterminedrule may include at least one of:

when the UE is scheduled to start receiving a first PDSCH starting insymbol j by a PDCCH ending in symbol i, the UE may not be expected to bescheduled to receive a second PDSCH with any time relation to the firstPDSCH with a PDCCH that ends also in symbol j from a second CORESETpool;

when the UE is scheduled to start receiving a first PDSCH starting insymbol j by a second PDCCH ending in symbol i, the UE may not beexpected to be scheduled to receive a PDSCH that overlaps with the firstPDSCH with a PDCCH that ends also in symbol j from a second CORESETpool; and/or

when the UE is scheduled to start receiving a first PDSCH starting insymbol j by a second PDCCH ending in symbol i, the UE may not beexpected to be scheduled to receive a PDSCH that does not overlap withthe first PDSCH with a PDCCH that ends also in symbol j from a secondCORESET pool.

In some embodiments, the UE may determine that at least two DCIs of themultiple DCIs do not end at a common symbol. In such embodiments, the UEmay determine, based on a second predetermined rule, when the UE may bescheduled to receive PDSCHs from CORESETs associated with the at leasttwo DCIs. In some embodiments, the second predetermined rule may includeat least one of:

when the UE is scheduled to start receiving a first PDSCH starting insymbol j by a PDCCH ending in symbol i, the UE may not be expected to bescheduled to receive a second PDSCH starting earlier than an end of thefirst PDSCH with a PDCCH that ends later than symbol i from a secondCORESET pool; and/or

when the UE is scheduled to start receiving a first PDSCH starting insymbol j by a PDCCH ending in symbol i, the UE may not be expected to bescheduled to receive a second PDSCH starting earlier than a first symbolof the first PDSCH with a PDCCH that ends later than symbol i from asecond CORESET pool.

In some embodiments, the UE may indicate support of single DCI multi-TRPoperation modes 1, 2a, 2b, 3, and 4 independently. In such embodiments,the UE may receive, from the base station, a configuration for a singleDCI multi-TRP operation mode the UE has indicated it does not supportand operate in a fall back mode.

In some embodiments, for multi-TRP multi-DCI based ultra reliable lowlatency communication (URLLC), the UE may receive multiple PDSCHs with acommon HARQ process ID overlapping in time. In some embodiments, formulti-TRP multi-DCI based URLLC, the UE may be scheduled to receive asecond PDSCH with a HARQ process ID common to a first PDSCH prior totransmission of an ACK/NACK associated with the first PDSCH.

In some embodiments, the UE may indicate that it does not support 2pre-coding matrix indexes (PMIs) sub-bands per channel quality indicator(CQI) sub-band for less than 20 PMI sub-bands.

In some embodiments, the UE may determine, based on a secondpredetermined rule, when the UE may be scheduled to transmit PUSCHs fromCORESETs associated with the at least two DCIs. In other words, the UEmay determine a possible relationship between the PUSCHs associated withthe at least 2 DCIs based on the second predetermined rule, e.g., anearliest possible starting/ending symbol of one PUSCH relative toanother PUSCH. In some embodiments, the second predetermined rule mayinclude at least one of no overlap between PUSCHs (e.g., a startingsymbol of one PUSCH does not occur until after an ending symbol ofanother PUSCH) or at least partial overlap between PUSCHs (e.g., astarting symbol of one PUSCH occurs prior to an ending symbol of anotherPUSCH).

In some embodiments, the second predetermined rule may be based on theindex value, e.g. the CORESETPool index. For example, when the secondpredetermined rule is based on the index value, the predetermined rulemay include at least one of:

when the UE is scheduled to start transmitting a first PUSCH starting insymbol j by a PDCCH from a first CORESET pool with an index value of 0and ending in symbol i, the UE may not be expected to be scheduled totransmit a second PUSCH starting earlier than the end of the first PUSCHwith a PDCCH that ends also in symbol j from a CORESET pool withnon-zero index value;

when the UE is scheduled to start transmitting a first PUSCH starting insymbol j by a PDCCH from a first CORESET pool with an index value of 0and ending in symbol i, the UE may not be expected to be scheduled totransmit a second PUSCH starting earlier than the first symbol of thefirst PUSCH with a PDCCH that ends also in symbol j from a CORESET poolwith non-zero index value; and/or

when the UE is scheduled to start transmitting a first PUSCH starting insymbol j by a PDCCH from a first CORESET pool with an index value 0ending in symbol i, the UE may not be expected to be scheduled totransmit a second PUSCH ending earlier than the first symbol of thefirst PUSCH with a PDCCH that ends also in symbol j from a CORESET poolwith non-zero index value.

In some embodiments, the second predetermined rule may be based on atiming relationship between the PUSCHs. In such embodiments, the secondpredetermined rule may include at least one of:

when the UE is scheduled to start transmitting a first PUSCH starting insymbol j by a PDCCH ending in symbol i, the UE may not be expected to bescheduled to transmit a second PUSCH with any time relation to the firstPUSCH with a PDCCH that ends also in symbol j from a second CORESETpool;

when the UE is scheduled to start transmitting a first PUSCH starting insymbol j by a second PDCCH ending in symbol i, the UE may not beexpected to be scheduled to receive a PUSCH that overlaps with the firstPUSCH with a PDCCH that ends also in symbol j from a second CORESETpool; and/or

when the UE is scheduled to start transmitting a first PUSCH starting insymbol j by a second PDCCH ending in symbol i, the UE may not beexpected to be scheduled to transmit a PUSCH that does not overlap withthe first PUSCH with a PDCCH that ends also in symbol j from a secondCORESET pool.

In some embodiments, the UE may determine that at least two DCIs of themultiple DCIs do not end at a common symbol. In such embodiments, the UEmay determine, based on a second predetermined rule, when the UE may bescheduled to transmit PUSCHs from CORESETs associated with the at leasttwo DCIs. In some embodiments, the second predetermined rule may includeat least one of:

when the UE is scheduled to start transmitting a first PUSCH starting insymbol j by a PDCCH ending in symbol i, the UE may not be expected to bescheduled to transmit a second PUSCH starting earlier than an end of thefirst PUSCH with a PDCCH that ends later than symbol i from a secondCORESET pool; and/or

when the UE is scheduled to start transmitting a first PUSCH starting insymbol j by a PDCCH ending in symbol i, the UE may not be expected to bescheduled to transmit a second PUSCH starting earlier than a firstsymbol of the first PUSCH with a PDCCH that ends later than symbol ifrom a second CORESET pool.

In some embodiments, the UE may determine, based on a thirdpredetermined rule, when the UE may be scheduled to transmitacknowledgments/negative acknowledgments (ACK/NACKs) from CORESETsassociated with the at least two DCIs. In other words, the UE maydetermine a possible relationship between ACK/NACKS for PDSCHsassociated with the at least 2 DCIs based on the third predeterminedrule. In some embodiments, the third predetermined rule may include atleast one of:

in a common slot, for a PDSCH scheduled by a second CORESET pool,ACK/NACKs may have any time relationship; and/or

in a common slot, for a PDSCH scheduled by a second CORESET pool, aCORESET pool having a non-zero index value may not schedule an ACK/NACKearlier than a slot scheduled by a CORESET pool having an index value of0 for ACK/NACK.

Turning to FIG. 12, illustrated is a block diagram of an example ofmulti-TRP operation for transmission, according to some embodiments. At1202, a UE, such as UE 106 may receive, from a base station, such asbase station 102, a configuration that may include multiple controlresource set (CORESET) pools. In some embodiments, each CORESET pool maybe associated with an index value, e.g., a CORESETPool index. In someembodiments, for each CORESET pool of the multiple CORESET pools, the UEmay:

for frequency division duplexing, monitor one unicast downlinktransmission and one unicast uplink transmission per slot per scheduledcomponent carrier per CORESET pool; and/or

for time division duplexing, monitor one unicast downlink transmissionand two unicast uplink transmissions per slot per scheduled componentcarrier per CORESET pool. In some embodiments, for each CORESET pool ofthe multiple CORESET pools, the UE may:

for frequency division duplexing, monitor one unicast downlinktransmission and one unicast uplink transmission per component carrierset of monitoring occasions per CORESET pool;

for time division duplexing, monitor one unicast downlink transmissionand two unicast uplink transmissions per component carrier set ofmonitoring occasions per CORESET pool; and/or

for time division duplexing, monitor two unicast downlink transmissionsand one unicast uplink transmission per component carrier set ofmonitoring occasions per CORESET pool.

At 1204, the UE may receive, from the base station, multiple downlinkcontrol indexes (DCIs). In some embodiments, each DCI may be associatedwith a CORESET pool, e.g., with a CORESET pool index value.

At 1206, the UE may determine that at least two DCIs of the multipleDCIs end at a common symbol. In other words, the UE may determine thatmore than one DCI ends at the same symbol.

At 1208, the UE may determine, based on a predetermined rule, when theUE may be scheduled to transmit PUSCHs from CORESETs associated with theat least two DCIs. In other words, the UE may determine a possiblerelationship between the PUSCHs associated with the at least 2 DCIsbased on the predetermined rule, e.g., an earliest possiblestarting/ending symbol of one PUSCH relative to another PUSCH. In someembodiments, the predetermined rule may include at least one of nooverlap between PUSCHs (e.g., a starting symbol of one PUSCH does notoccur until after an ending symbol of another PUSCH) or at least partialoverlap between PUSCHs (e.g., a starting symbol of one PUSCH occursprior to an ending symbol of another PUSCH).

In some embodiments, the predetermined rule may be based on the indexvalue, e.g. the CORESETPool index. For example, when the predeterminedrule is based on the index value, the predetermined rule may include atleast one of:

when the UE is scheduled to start transmitting a first PUSCH starting insymbol j by a PDCCH from a first CORESET pool with an index value of 0and ending in symbol i, the UE may not be expected to be scheduled totransmit a second PUSCH starting earlier than the end of the first PUSCHwith a PDCCH that ends also in symbol j from a CORESET pool withnon-zero index value;

when the UE is scheduled to start transmitting a first PUSCH starting insymbol j by a PDCCH from a first CORESET pool with an index value of 0and ending in symbol i, the UE may not be expected to be scheduled totransmit a second PUSCH starting earlier than the first symbol of thefirst PUSCH with a PDCCH that ends also in symbol j from a CORESET poolwith non-zero index value; and/or

when the UE is scheduled to start transmitting a first PUSCH starting insymbol j by a PDCCH from a first CORESET pool with an index value 0ending in symbol i, the UE may not be expected to be scheduled totransmit a second PUSCH ending earlier than the first symbol of thefirst PUSCH with a PDCCH that ends also in symbol j from a CORESET poolwith non-zero index value.

In some embodiments, the predetermined rule may be based on a timingrelationship between the PUSCHs. In such embodiments, the predeterminedrule may include at least one of:

when the UE is scheduled to start transmitting a first PUSCH starting insymbol j by a PDCCH ending in symbol i, the UE may not be expected to bescheduled to transmit a second PUSCH with any time relation to the firstPUSCH with a PDCCH that ends also in symbol j from a second CORESETpool;

when the UE is scheduled to start transmitting a first PUSCH starting insymbol j by a second PDCCH ending in symbol i, the UE may not beexpected to be scheduled to receive a PUSCH that overlaps with the firstPUSCH with a PDCCH that ends also in symbol j from a second CORESETpool; and/or

when the UE is scheduled to start transmitting a first PUSCH starting insymbol j by a second PDCCH ending in symbol i, the UE may not beexpected to be scheduled to transmit a PUSCH that does not overlap withthe first PUSCH with a PDCCH that ends also in symbol j from a secondCORESET pool.

In some embodiments, the UE may determine that at least two DCIs of themultiple DCIs do not end at a common symbol. In such embodiments, the UEmay determine, based on a predetermined rule, when the UE may bescheduled to transmit PUSCHs from CORESETs associated with the at leasttwo DCIs. In some embodiments, the predetermined rule may include atleast one of:

when the UE is scheduled to start transmitting a first PUSCH starting insymbol j by a PDCCH ending in symbol i, the UE may not be expected to bescheduled to transmit a second PUSCH starting earlier than an end of thefirst PUSCH with a PDCCH that ends later than symbol i from a secondCORESET pool; and/or

when the UE is scheduled to start transmitting a first PUSCH starting insymbol j by a PDCCH ending in symbol i, the UE may not be expected to bescheduled to transmit a second PUSCH starting earlier than a firstsymbol of the first PUSCH with a PDCCH that ends later than symbol ifrom a second CORESET pool.

In some embodiments, the UE may indicate support of single DCI multi-TRPoperation modes 1, 2a, 2b, 3, and 4 independently. In such embodiments,the UE may receive, from the base station, a configuration for a singleDCI multi-TRP operation mode the UE has indicated it does not supportand operate in a fall back mode.

In some embodiments, for multi-TRP multi-DCI based ultra reliable lowlatency communication (URLLC), the UE may receive multiple PDSCHs with acommon HARQ process ID overlapping in time. In some embodiments, formulti-TRP multi-DCI based URLLC, the UE may be scheduled to receive asecond PDSCH with a HARQ process ID common to a first PDSCH prior totransmission of an ACK/NACK associated with the first PDSCH.

In some embodiments, the UE may indicate that it does not support 2pre-coding matrix indexes (PMIs) sub-bands per channel quality indicator(CQI) sub-band for less than 20 PMI sub-bands.

In some embodiments, the UE may determine, based on a secondpredetermined rule when the UE is scheduled to receive physical downlinkcontrol channels (PDSCHs) from CORESETs associated with the at least twoDCIs. In other words, the UE may determine a possible relationshipbetween the PDSCHs associated with the at least 2 DCIs based on thesecond predetermined rule, e.g., an earliest possible starting/endingsymbol of one PDSCH relative to another PDSCH. In some embodiments, thesecond predetermined rule may include at least one of no overlap betweenPDSCHs (e.g., a starting symbol of one PDSCH does not occur until afteran ending symbol of another PDSCH) or at least partial overlap betweenPDSCHs (e.g., a starting symbol of one PDSCH occurs prior to an endingsymbol of another PDSCH).

In some embodiments, the second predetermined rule may be based on theindex value, e.g. the CORESETPool index. For example, when the secondpredetermined rule is based on the index value, the second predeterminedrule may include at least one of:

when the UE is scheduled to start receiving a first PDSCH starting insymbol j by a physical downlink control channel (PDCCH) from a firstCORESET pool with an index value of 0 and ending in symbol i, the UE maynot be expected to be scheduled to receive a second PDSCH startingearlier than the end of the first PDSCH with a PDCCH that ends also insymbol j from a CORESET pool with non-zero index value;

when the UE is scheduled to start receiving a first PDSCH starting insymbol j by a PDCCH from a first CORESET pool with an index value of 0and ending in symbol i, the UE may not be expected to be scheduled toreceive a second PDSCH starting earlier than the first symbol of thefirst PDSCH with a PDCCH that ends also in symbol j from a CORESET poolwith non-zero index value; and/or

when the UE is scheduled to start receiving a first PDSCH starting insymbol j by a PDCCH from a first CORESET pool with an index value 0ending in symbol i, the UE may not be expected to be scheduled toreceive a second PDSCH ending earlier than the first symbol of the firstPDSCH with a PDCCH that ends also in symbol j from a CORESET pool withnon-zero index value.

In some embodiments, the second predetermined rule may be based on atiming relationship between the PDSCHs. In such embodiments, the secondpredetermined rule may include at least one of:

when the UE is scheduled to start receiving a first PDSCH starting insymbol j by a PDCCH ending in symbol i, the UE may not be expected to bescheduled to receive a second PDSCH with any time relation to the firstPDSCH with a PDCCH that ends also in symbol j from a second CORESETpool;

when the UE is scheduled to start receiving a first PDSCH starting insymbol j by a second PDCCH ending in symbol i, the UE may not beexpected to be scheduled to receive a PDSCH that overlaps with the firstPDSCH with a PDCCH that ends also in symbol j from a second CORESETpool; and/or

when the UE is scheduled to start receiving a first PDSCH starting insymbol j by a second PDCCH ending in symbol i, the UE may not beexpected to be scheduled to receive a PDSCH that does not overlap withthe first PDSCH with a PDCCH that ends also in symbol j from a secondCORESET pool.

In some embodiments, the UE may determine that at least two DCIs of themultiple DCIs do not end at a common symbol. In such embodiments, the UEmay determine, based on a second predetermined rule, when the UE may bescheduled to receive PDSCHs from CORESETs associated with the at leasttwo DCIs. In some embodiments, the second predetermined rule may includeat least one of:

when the UE is scheduled to start receiving a first PDSCH starting insymbol j by a PDCCH ending in symbol i, the UE may not be expected to bescheduled to receive a second PDSCH starting earlier than an end of thefirst PDSCH with a PDCCH that ends later than symbol i from a secondCORESET pool; and/or

when the UE is scheduled to start receiving a first PDSCH starting insymbol j by a PDCCH ending in symbol i, the UE may not be expected to bescheduled to receive a second PDSCH starting earlier than a first symbolof the first PDSCH with a PDCCH that ends later than symbol i from asecond CORESET pool.

In some embodiments, the UE may determine, based on a thirdpredetermined rule, when the UE may be scheduled to transmitacknowledgments/negative acknowledgments (ACK/NACKs) from CORESETsassociated with the at least two DCIs. In other words, the UE maydetermine a possible relationship between ACK/NACKS for PDSCHsassociated with the at least 2 DCIs based on the third predeterminedrule. In some embodiments, the third predetermined rule may include atleast one of:

in a common slot, for a PDSCH scheduled by a second CORESET pool,ACK/NACKs may have any time relationship; and/or

in a common slot, for a PDSCH scheduled by a second CORESET pool, aCORESET pool having a non-zero index value may not schedule an ACK/NACKearlier than a slot scheduled by a CORESET pool having an index value of0 for ACK/NACK.

Turning to FIG. 13, illustrated is a block diagram of an example ofmulti-TRP operation for ACK/NACK, according to some embodiments. At1302, a UE, such as UE 106 may receive, from a base station, such asbase station 102, a configuration that may include multiple controlresource set (CORESET) pools. In some embodiments, each CORESET pool maybe associated with an index value, e.g., a CORESETPool index. In someembodiments, for each CORESET pool of the multiple CORESET pools, the UEmay:

for frequency division duplexing, monitor one unicast downlinktransmission and one unicast uplink transmission per slot per scheduledcomponent carrier per CORESET pool; and/or

for time division duplexing, monitor one unicast downlink transmissionand two unicast uplink transmissions per slot per scheduled componentcarrier per CORESET pool. In some embodiments, for each CORESET pool ofthe multiple CORESET pools, the UE may:

for frequency division duplexing, monitor one unicast downlinktransmission and one unicast uplink transmission per component carrierset of monitoring occasions per CORESET pool;

for time division duplexing, monitor one unicast downlink transmissionand two unicast uplink transmissions per component carrier set ofmonitoring occasions per CORESET pool; and/or

for time division duplexing, monitor two unicast downlink transmissionsand one unicast uplink transmission per component carrier set ofmonitoring occasions per CORESET pool.

At 1304, the UE may receive, from the base station, multiple downlinkcontrol indexes (DCIs). In some embodiments, each DCI may be associatedwith a CORESET pool, e.g., with a CORESET pool index value.

At 1306, the UE may determine that at least two DCIs of the multipleDCIs end at a common symbol. In other words, the UE may determine thatmore than one DCI ends at the same symbol.

At 1308, the UE may determine, based on a predetermined rule, when theUE may be scheduled to transmit acknowledgments/negative acknowledgments(ACK/NACKs) from CORESETs associated with the at least two DCIs. Inother words, the UE may determine a possible relationship betweenACK/NACKS for PDSCHs associated with the at least 2 DCIs based on thepredetermined rule. In some embodiments, the predetermined rule mayinclude at least one of:

in a common slot, for a PDSCH scheduled by a second CORESET pool,ACK/NACKs may have any time relationship; and/or

in a common slot, for a PDSCH scheduled by a second CORESET pool, aCORESET pool having a non-zero index value may not schedule an ACK/NACKearlier than a slot scheduled by a CORESET pool having an index value of0 for ACK/NACK.

In some embodiments, the UE may indicate support of single DCI multi-TRPoperation modes 1, 2a, 2b, 3, and 4 independently. In such embodiments,the UE may receive, from the base station, a configuration for a singleDCI multi-TRP operation mode the UE has indicated it does not supportand operate in a fall back mode.

In some embodiments, for multi-TRP multi-DCI based ultra reliable lowlatency communication (URLLC), the UE may receive multiple PDSCHs with acommon HARQ process ID overlapping in time. In some embodiments, formulti-TRP multi-DCI based URLLC, the UE may be scheduled to receive asecond PDSCH with a HARQ process ID common to a first PDSCH prior totransmission of an ACK/NACK associated with the first PDSCH.

In some embodiments, the UE may indicate that it does not support 2pre-coding matrix indexes (PMIs) sub-bands per channel quality indicator(CQI) sub-band for less than 20 PMI sub-bands.

In some embodiments, the UE may determine, based on a secondpredetermined rule when the UE is scheduled to receive physical downlinkcontrol channels (PDSCHs) from CORESETs associated with the at least twoDCIs. In other words, the UE may determine a possible relationshipbetween the PDSCHs associated with the at least 2 DCIs based on thesecond predetermined rule, e.g., an earliest possible starting/endingsymbol of one PDSCH relative to another PDSCH. In some embodiments, thesecond predetermined rule may include at least one of no overlap betweenPDSCHs (e.g., a starting symbol of one PDSCH does not occur until afteran ending symbol of another PDSCH) or at least partial overlap betweenPDSCHs (e.g., a starting symbol of one PDSCH occurs prior to an endingsymbol of another PDSCH).

In some embodiments, the second predetermined rule may be based on theindex value, e.g. the CORESETPool index. For example, when the secondpredetermined rule is based on the index value, the second predeterminedrule may include at least one of:

when the UE is scheduled to start receiving a first PDSCH starting insymbol j by a physical downlink control channel (PDCCH) from a firstCORESET pool with an index value of 0 and ending in symbol i, the UE maynot be expected to be scheduled to receive a second PDSCH startingearlier than the end of the first PDSCH with a PDCCH that ends also insymbol j from a CORESET pool with non-zero index value;

when the UE is scheduled to start receiving a first PDSCH starting insymbol j by a PDCCH from a first CORESET pool with an index value of 0and ending in symbol i, the UE may not be expected to be scheduled toreceive a second PDSCH starting earlier than the first symbol of thefirst PDSCH with a PDCCH that ends also in symbol j from a CORESET poolwith non-zero index value; and/or

when the UE is scheduled to start receiving a first PDSCH starting insymbol j by a PDCCH from a first CORESET pool with an index value 0ending in symbol i, the UE may not be expected to be scheduled toreceive a second PDSCH ending earlier than the first symbol of the firstPDSCH with a PDCCH that ends also in symbol j from a CORESET pool withnon-zero index value.

In some embodiments, the second predetermined rule may be based on atiming relationship between the PDSCHs. In such embodiments, the secondpredetermined rule may include at least one of:

when the UE is scheduled to start receiving a first PDSCH starting insymbol j by a PDCCH ending in symbol i, the UE may not be expected to bescheduled to receive a second PDSCH with any time relation to the firstPDSCH with a PDCCH that ends also in symbol j from a second CORESETpool;

when the UE is scheduled to start receiving a first PDSCH starting insymbol j by a second PDCCH ending in symbol i, the UE may not beexpected to be scheduled to receive a PDSCH that overlaps with the firstPDSCH with a PDCCH that ends also in symbol j from a second CORESETpool; and/or

when the UE is scheduled to start receiving a first PDSCH starting insymbol j by a second PDCCH ending in symbol i, the UE may not beexpected to be scheduled to receive a PDSCH that does not overlap withthe first PDSCH with a PDCCH that ends also in symbol j from a secondCORESET pool.

In some embodiments, the UE may determine that at least two DCIs of themultiple DCIs do not end at a common symbol. In such embodiments, the UEmay determine, based on a second predetermined rule, when the UE may bescheduled to receive PDSCHs from CORESETs associated with the at leasttwo DCIs. In some embodiments, the second predetermined rule may includeat least one of:

when the UE is scheduled to start receiving a first PDSCH starting insymbol j by a PDCCH ending in symbol i, the UE may not be expected to bescheduled to receive a second PDSCH starting earlier than an end of thefirst PDSCH with a PDCCH that ends later than symbol i from a secondCORESET pool; and/or

when the UE is scheduled to start receiving a first PDSCH starting insymbol j by a PDCCH ending in symbol i, the UE may not be expected to bescheduled to receive a second PDSCH starting earlier than a first symbolof the first PDSCH with a PDCCH that ends later than symbol i from asecond CORESET pool.

In some embodiments, the UE may determine, based on a thirdpredetermined rule, when the UE may be scheduled to transmit PUSCHs fromCORESETs associated with the at least two DCIs. In other words, the UEmay determine a possible relationship between the PUSCHs associated withthe at least 2 DCIs based on the third predetermined rule, e.g., anearliest possible starting/ending symbol of one PUSCH relative toanother PUSCH. In some embodiments, the third predetermined rule mayinclude at least one of no overlap between PUSCHs (e.g., a startingsymbol of one PUSCH does not occur until after an ending symbol ofanother PUSCH) or at least partial overlap between PUSCHs (e.g., astarting symbol of one PUSCH occurs prior to an ending symbol of anotherPUSCH).

In some embodiments, the third predetermined rule may be based on theindex value, e.g. the CORESETPool index. For example, when the thirdpredetermined rule is based on the index value, the predetermined rulemay include at least one of:

when the UE is scheduled to start transmitting a first PUSCH starting insymbol j by a PDCCH from a first CORESET pool with an index value of 0and ending in symbol i, the UE may not be expected to be scheduled totransmit a second PUSCH starting earlier than the end of the first PUSCHwith a PDCCH that ends also in symbol j from a CORESET pool withnon-zero index value;

when the UE is scheduled to start transmitting a first PUSCH starting insymbol j by a PDCCH from a first CORESET pool with an index value of 0and ending in symbol i, the UE may not be expected to be scheduled totransmit a second PUSCH starting earlier than the first symbol of thefirst PUSCH with a PDCCH that ends also in symbol j from a CORESET poolwith non-zero index value; and/or

when the UE is scheduled to start transmitting a first PUSCH starting insymbol j by a PDCCH from a first CORESET pool with an index value 0ending in symbol i, the UE may not be expected to be scheduled totransmit a second PUSCH ending earlier than the first symbol of thefirst PUSCH with a PDCCH that ends also in symbol j from a CORESET poolwith non-zero index value.

In some embodiments, the third predetermined rule may be based on atiming relationship between the PUSCHs. In such embodiments, the thirdpredetermined rule may include at least one of:

when the UE is scheduled to start transmitting a first PUSCH starting insymbol j by a PDCCH ending in symbol i, the UE may not be expected to bescheduled to transmit a second PUSCH with any time relation to the firstPUSCH with a PDCCH that ends also in symbol j from a second CORESETpool;

when the UE is scheduled to start transmitting a first PUSCH starting insymbol j by a second PDCCH ending in symbol i, the UE may not beexpected to be scheduled to receive a PUSCH that overlaps with the firstPUSCH with a PDCCH that ends also in symbol j from a second CORESETpool; and/or

when the UE is scheduled to start transmitting a first PUSCH starting insymbol j by a second PDCCH ending in symbol i, the UE may not beexpected to be scheduled to transmit a PUSCH that does not overlap withthe first PUSCH with a PDCCH that ends also in symbol j from a secondCORESET pool.

In some embodiments, the UE may determine that at least two DCIs of themultiple DCIs do not end at a common symbol. In such embodiments, the UEmay determine, based on a third predetermined rule, when the UE may bescheduled to transmit PUSCHs from CORESETs associated with the at leasttwo DCIs. In some embodiments, the third predetermined rule may includeat least one of:

when the UE is scheduled to start transmitting a first PUSCH starting insymbol j by a PDCCH ending in symbol i, the UE may not be expected to bescheduled to transmit a second PUSCH starting earlier than an end of thefirst PUSCH with a PDCCH that ends later than symbol i from a secondCORESET pool; and/or

when the UE is scheduled to start transmitting a first PUSCH starting insymbol j by a PDCCH ending in symbol i, the UE may not be expected to bescheduled to transmit a second PUSCH starting earlier than a firstsymbol of the first PUSCH with a PDCCH that ends later than symbol ifrom a second CORESET pool.

Turning to FIG. 14, illustrated is a block diagram of an example ofmulti-TRP operation for reception, according to some embodiments. At1402, a UE, such as UE 106 may receive, from a base station, such asbase station 102, a configuration that may include multiple controlresource set (CORESET) pools. In some embodiments, each CORESET pool maybe associated with an index value, e.g., a CORESETPool index. In someembodiments, for each CORESET pool of the multiple CORESET pools, the UEmay:

for frequency division duplexing, monitor one unicast downlinktransmission and one unicast uplink transmission per slot per scheduledcomponent carrier per CORESET pool; and/or

for time division duplexing, monitor one unicast downlink transmissionand two unicast uplink transmissions per slot per scheduled componentcarrier per CORESET pool. In some embodiments, for each CORESET pool ofthe multiple CORESET pools, the UE may:

for frequency division duplexing, monitor one unicast downlinktransmission and one unicast uplink transmission per component carrierset of monitoring occasions per CORESET pool;

for time division duplexing, monitor one unicast downlink transmissionand two unicast uplink transmissions per component carrier set ofmonitoring occasions per CORESET pool; and/or

for time division duplexing, monitor two unicast downlink transmissionsand one unicast uplink transmission per component carrier set ofmonitoring occasions per CORESET pool.

At 1404, the UE may receive, from the base station, multiple downlinkcontrol indexes (DCIs). In some embodiments, each DCI may be associatedwith a CORESET pool, e.g., with a CORESET pool index value.

At 1406, the UE may determine that at least two DCIs of the multipleDCIs end at a common symbol. In other words, the UE may determine thatmore than one DCI ends at the same symbol.

At 1408, the UE may determine, based on one or more predetermined rules,when the UE may be scheduled to receive PDSCHs, transmit PUSCHs, and/ortransmit ACK/NACKs from CORESETs associated with the at least two DCIs.For example, the UE may determine a possible relationship between thePDSCHs associated with the at least 2 DCIs based on a firstpredetermined rule of the one or more predetermined rules, e.g., anearliest possible starting/ending symbol of one PDSCH relative toanother PDSCH. In some embodiments, the first predetermined rule mayinclude at least one of no overlap between PDSCHs (e.g., a startingsymbol of one PDSCH does not occur until after an ending symbol ofanother PDSCH) or at least partial overlap between PDSCHs (e.g., astarting symbol of one PDSCH occurs prior to an ending symbol of anotherPDSCH). As another example, the UE may determine a possible relationshipbetween the PUSCHs associated with the at least 2 DCIs based on a secondpredetermine rule of the one or more predetermined rules, e.g., anearliest possible starting/ending symbol of one PUSCH relative toanother PUSCH. In some embodiments, the second predetermined rule mayinclude at least one of no overlap between PUSCHs (e.g., a startingsymbol of one PUSCH does not occur until after an ending symbol ofanother PUSCH) or at least partial overlap between PUSCHs (e.g., astarting symbol of one PUSCH occurs prior to an ending symbol of anotherPUSCH). As a further example, the UE may determine a possiblerelationship between ACK/NACKS for PDSCHs from CORESETs associated withthe at least two DCIs based on a third predetermined rule of the one ormore predetermined rules.

In some embodiments, the first predetermined rule may be based on theindex value, e.g. the CORESETPool index. For example, when the firstpredetermined rule is based on the index value, the first predeterminedrule may include at least one of:

when the UE is scheduled to start receiving a first PDSCH starting insymbol j by a physical downlink control channel (PDCCH) from a firstCORESET pool with an index value of 0 and ending in symbol i, the UE maynot be expected to be scheduled to receive a second PDSCH startingearlier than the end of the first PDSCH with a PDCCH that ends also insymbol j from a CORESET pool with non-zero index value;

when the UE is scheduled to start receiving a first PDSCH starting insymbol j by a PDCCH from a first CORESET pool with an index value of 0and ending in symbol i, the UE may not be expected to be scheduled toreceive a second PDSCH starting earlier than the first symbol of thefirst PDSCH with a PDCCH that ends also in symbol j from a CORESET poolwith non-zero index value; and/or

when the UE is scheduled to start receiving a first PDSCH starting insymbol j by a PDCCH from a first CORESET pool with an index value 0ending in symbol i, the UE may not be expected to be scheduled toreceive a second PDSCH ending earlier than the first symbol of the firstPDSCH with a PDCCH that ends also in symbol j from a CORESET pool withnon-zero index value.

In some embodiments, the first predetermined rule may be based on atiming relationship between the PDSCHs. In such embodiments, the firstpredetermined rule may include at least one of:

when the UE is scheduled to start receiving a first PDSCH starting insymbol j by a PDCCH ending in symbol i, the UE may not be expected to bescheduled to receive a second PDSCH with any time relation to the firstPDSCH with a PDCCH that ends also in symbol j from a second CORESETpool;

when the UE is scheduled to start receiving a first PDSCH starting insymbol j by a second PDCCH ending in symbol i, the UE may not beexpected to be scheduled to receive a PDSCH that overlaps with the firstPDSCH with a PDCCH that ends also in symbol j from a second CORESETpool; and/or

when the UE is scheduled to start receiving a first PDSCH starting insymbol j by a second PDCCH ending in symbol i, the UE may not beexpected to be scheduled to receive a PDSCH that does not overlap withthe first PDSCH with a PDCCH that ends also in symbol j from a secondCORESET pool.

In some embodiments, the second predetermined rule may be based on theindex value, e.g. the CORESETPool index. For example, when the secondpredetermined rule is based on the index value, the predetermined rulemay include at least one of:

when the UE is scheduled to start transmitting a first PUSCH starting insymbol j by a PDCCH from a first CORESET pool with an index value of 0and ending in symbol i, the UE may not be expected to be scheduled totransmit a second PUSCH starting earlier than the end of the first PUSCHwith a PDCCH that ends also in symbol j from a CORESET pool withnon-zero index value;

when the UE is scheduled to start transmitting a first PUSCH starting insymbol j by a PDCCH from a first CORESET pool with an index value of 0and ending in symbol i, the UE may not be expected to be scheduled totransmit a second PUSCH starting earlier than the first symbol of thefirst PUSCH with a PDCCH that ends also in symbol j from a CORESET poolwith non-zero index value; and/or

when the UE is scheduled to start transmitting a first PUSCH starting insymbol j by a PDCCH from a first CORESET pool with an index value 0ending in symbol i, the UE may not be expected to be scheduled totransmit a second PUSCH ending earlier than the first symbol of thefirst PUSCH with a PDCCH that ends also in symbol j from a CORESET poolwith non-zero index value.

In some embodiments, the second predetermined rule may be based on atiming relationship between the PUSCHs. In such embodiments, the secondpredetermined rule may include at least one of:

when the UE is scheduled to start transmitting a first PUSCH starting insymbol j by a PDCCH ending in symbol i, the UE may not be expected to bescheduled to transmit a second PUSCH with any time relation to the firstPUSCH with a PDCCH that ends also in symbol j from a second CORESETpool;

when the UE is scheduled to start transmitting a first PUSCH starting insymbol j by a second PDCCH ending in symbol i, the UE may not beexpected to be scheduled to receive a PUSCH that overlaps with the firstPUSCH with a PDCCH that ends also in symbol j from a second CORESETpool; and/or

when the UE is scheduled to start transmitting a first PUSCH starting insymbol j by a second PDCCH ending in symbol i, the UE may not beexpected to be scheduled to transmit a PUSCH that does not overlap withthe first PUSCH with a PDCCH that ends also in symbol j from a secondCORESET pool.

In some embodiments, the third predetermined rule may include at leastone of:

in a common slot, for a PDSCH scheduled by a second CORESET pool,ACK/NACKs may have any time relationship; and/or

in a common slot, for a PDSCH scheduled by a second CORESET pool, aCORESET pool having a non-zero index value may not schedule an ACK/NACKearlier than a slot scheduled by a CORESET pool having an index value of0 for ACK/NACK.

In some embodiments, the UE may determine that at least two DCIs of themultiple DCIs do not end at a common symbol. In such embodiments, the UEmay determine, based on a fourth predetermined rule of the one or morepredetermined rules, when the UE may be scheduled to receive PDSCHs fromCORESETs associated with the at least two DCIs. Similarly, the UE maydetermine, based on a fifth predetermined rule of the one or morepredetermined rules, when the UE may be scheduled to transmit PUSCHsfrom CORESETs associated with the at least two DCIs.

In some embodiments, the fourth predetermined rule may include at leastone of:

when the UE is scheduled to start receiving a first PDSCH starting insymbol j by a PDCCH ending in symbol i, the UE may not be expected to bescheduled to receive a second PDSCH starting earlier than an end of thefirst PDSCH with a PDCCH that ends later than symbol i from a secondCORESET pool; and/or

when the UE is scheduled to start receiving a first PDSCH starting insymbol j by a PDCCH ending in symbol i, the UE may not be expected to bescheduled to receive a second PDSCH starting earlier than a first symbolof the first PDSCH with a PDCCH that ends later than symbol i from asecond CORESET pool.

In some embodiments, the fifth predetermined rule may include at leastone of:

when the UE is scheduled to start transmitting a first PUSCH starting insymbol j by a PDCCH ending in symbol i, the UE may not be expected to bescheduled to transmit a second PUSCH starting earlier than an end of thefirst PUSCH with a PDCCH that ends later than symbol i from a secondCORESET pool; and/or

when the UE is scheduled to start transmitting a first PUSCH starting insymbol j by a PDCCH ending in symbol i, the UE may not be expected to bescheduled to transmit a second PUSCH starting earlier than a firstsymbol of the first PUSCH with a PDCCH that ends later than symbol ifrom a second CORESET pool.

In some embodiments, the UE may indicate support of single DCI multi-TRPoperation modes 1, 2a, 2b, 3, and 4 independently. In such embodiments,the UE may receive, from the base station, a configuration for a singleDCI multi-TRP operation mode the UE has indicated it does not supportand operate in a fall back mode.

In some embodiments, for multi-TRP multi-DCI based ultra reliable lowlatency communication (URLLC), the UE may receive multiple PDSCHs with acommon HARQ process ID overlapping in time. In some embodiments, formulti-TRP multi-DCI based URLLC, the UE may be scheduled to receive asecond PDSCH with a HARQ process ID common to a first PDSCH prior totransmission of an ACK/NACK associated with the first PDSCH.

In some embodiments, the UE may indicate that it does not support 2pre-coding matrix indexes (PMIs) sub-bands per channel quality indicator(CQI) sub-band for less than 20 PMI sub-bands.

It is well understood that the use of personally identifiableinformation should follow privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining the privacy of users. In particular,personally identifiable information data should be managed and handledso as to minimize risks of unintentional or unauthorized access or use,and the nature of authorized use should be clearly indicated to users.

Embodiments of the present disclosure may be realized in any of variousforms. For example, some embodiments may be realized as acomputer-implemented method, a computer-readable memory medium, or acomputer system. Other embodiments may be realized using one or morecustom-designed hardware devices such as ASICs. Still other embodimentsmay be realized using one or more programmable hardware elements such asFPGAs.

In some embodiments, a non-transitory computer-readable memory mediummay be configured so that it stores program instructions and/or data,where the program instructions, if executed by a computer system, causethe computer system to perform a method, e.g., any of the methodembodiments described herein, or, any combination of the methodembodiments described herein, or, any subset of any of the methodembodiments described herein, or, any combination of such subsets.

In some embodiments, a device (e.g., a UE 106) may be configured toinclude a processor (or a set of processors) and a memory medium, wherethe memory medium stores program instructions, where the processor isconfigured to read and execute the program instructions from the memorymedium, where the program instructions are executable to implement anyof the various method embodiments described herein (or, any combinationof the method embodiments described herein, or, any subset of any of themethod embodiments described herein, or, any combination of suchsubsets). The device may be realized in any of various forms.

Although the embodiments above have been described in considerabledetail, numerous variations and modifications will become apparent tothose skilled in the art once the above disclosure is fully appreciated.It is intended that the following claims be interpreted to embrace allsuch variations and modifications.

What is claimed is:
 1. A user equipment device (UE), comprising: atleast one antenna; at least one radio, wherein the at least one radio isconfigured to perform cellular communication using at least one radioaccess technology (RAT); one or more processors coupled to the at leastone radio, wherein the one or more processors and the at least one radioare configured to perform voice and/or data communications; wherein theone or more processors are configured to cause the UE to: receive, froma base station, a configuration including multiple control resource set(CORESET) pools, wherein each CORESET pool is associated with an indexvalue; receive multiple downlink control indexes (DCIs); determine afirst DCI of the multiple DCIs ends at a first symbol; determine asecond DCI of the multiple DCIs ends at a second symbol later than thefirst symbol: and for any two hybrid automatic repeat request (HARQ)process identifiers (IDs) in a given scheduled cell, when the first DCIand the second DCI are associated with different CORESET pool indexvalues, determine physical downlink shared channels (PDSCHs) fromCORESETs associated with the first and second DCIs can be partially orfully overlapped in time.
 2. The UE of claim 1, wherein the one or moreprocessors are further configured to cause the UE to: for any two HARQIDs in the given scheduled cell, when the first DCI and the second DCIare not associated with different CORESET pool index values, determinethe UE is not expected to be scheduled to receive a PDSCH associatedwith the second DCI starting earlier than an end of a first PDSCHassociated with the first DCI.
 3. The UE of claim 1, wherein the one ormore processors are further configured to cause the UE to: determine,based on the one or more predetermined rules, at least one of: when theUE is scheduled to receive PDSCHs from CORESETs associated with thefirst DCI and the second DCI; when the UE is scheduled to transmitphysical uplink shared channels (PUSCHs) from CORESETs associated withthe first DCI and the second DCI; or when the UE is scheduled totransmit acknowledgments/negative acknowledgments from CORESETsassociated with the first DCI and the second DCI.
 4. The UE of claim 3,wherein a first predetermined rule of the one or more predeterminedrules includes at least one of: when the UE is scheduled to startreceiving a first PDSCH starting in symbol j by a PDCCH ending in symboli, the UE is not expected to be scheduled to receive a second PDSCHstarting earlier than an end of the first PDSCH with a PDCCH that endslater than symbol i from a second CORESET pool; or when the UE isscheduled to start receiving a first PDSCH starting in symbol j by aPDCCH ending in symbol i, the UE is not expected to be scheduled toreceive a second PDSCH starting earlier than a first symbol of the firstPDSCH with a PDCCH that ends later than symbol i from a second CORESETpool; and wherein a second predetermined rule of the one or morepredetermined rules includes at least one of: when the UE is scheduledto start transmitting a first PUSCH starting in symbol j by a PDCCHending in symbol i, the UE is not expected to be scheduled to transmit asecond PUSCH starting earlier than an end of the first PUSCH with aPDCCH that ends later than symbol i from a second CORESET pool; or whenthe UE is scheduled to start transmitting a first PUSCH starting insymbol j by a PDCCH ending in symbol i, the UE is not expected to bescheduled to transmit a second PUSCH starting earlier than a firstsymbol of the first PUSCH with a PDCCH that ends later than symbol ifrom a second CORESET pool.
 5. The UE of claim 1, wherein the one ormore processors are further configured to cause the UE to: determinethat at least two DCIs of the multiple DCIs ends at a common symbol; anddetermine, based on one or more predetermined rules, at least one of:when the UE is scheduled to receive PDSCHs from CORESETs associated withthe at least two DCIs; when the UE is scheduled to transmit physicaluplink shared channels (PUSCHs) from CORESETs associated with the atleast two DCIs; or when the UE is scheduled to transmitacknowledgments/negative acknowledgments from CORESETs associated withthe at least two DCIs.
 6. The UE of claim 5, wherein a firstpredetermined rule of the one or more predetermined rules includes atleast one of no overlapping of PDSCHs or at least partial overlapping ofPDSCHs.
 7. The UE of claim 5, wherein a first predetermined rule of theone or more predetermined rules is based on the index value.
 8. The UEof claim 7, wherein the first predetermined rule includes at least oneof: when the UE is scheduled to start receiving a first PDSCH startingin symbol j by a PDCCH from a first CORESET pool with an index value of0 and ending in symbol i, the UE is not expected to be scheduled toreceive a second PDSCH starting earlier than the end of the first PDSCHwith a PDCCH that ends also in symbol j from a CORESET pool withnon-zero index value; when the UE is scheduled to start receiving afirst PDSCH starting in symbol j by a PDCCH from a first CORESET poolwith an index value of 0 and ending in symbol i, the UE is not expectedto be scheduled to receive a second PDSCH starting earlier than thefirst symbol of the first PDSCH with a PDCCH that ends also in symbol jfrom a CORESET pool with non-zero index value; or when the UE isscheduled to start receiving a first PDSCH starting in symbol j by aPDCCH from a first CORESET pool with an index value 0 ending in symboli, the UE is not expected to be scheduled to receive a second PDSCHending earlier than the first symbol of the first PDSCH with a PDCCHthat ends also in symbol j from a CORESET pool with non-zero indexvalue.
 9. The UE of claim 7, wherein the first predetermined ruleincludes at least one of: when the UE is scheduled to start transmittinga first PUSCH starting in symbol j by a PDCCH from a first CORESET poolwith an index value of 0 and ending in symbol i, the UE is not expectedto be scheduled to transmit a second PUSCH starting earlier than the endof the first PUSCH with a PDCCH that ends also in symbol j from aCORESET pool with non-zero index value; when the UE is scheduled tostart transmitting a first PUSCH starting in symbol j by a PDCCH from afirst CORESET pool with an index value of 0 and ending in symbol i, theUE is not expected to be scheduled to transmit a second PUSCH startingearlier than the first symbol of the first PUSCH with a PDCCH that endsalso in symbol j from a CORESET pool with non-zero index value; or whenthe UE is scheduled to start transmitting a first PUSCH starting insymbol j by a PDCCH from a first CORESET pool with an index value 0ending in symbol i, the UE is not expected to be scheduled to transmit asecond PUSCH ending earlier than the first symbol of the first PUSCHwith a PDCCH that ends also in symbol j from a CORESET pool withnon-zero index value.
 10. The UE of claim 5, wherein a firstpredetermined rule of the one or more predetermined rules includes atleast one of: when the UE is scheduled to start receiving a first PDSCHstarting in symbol j by a PDCCH ending in symbol i, the UE is notexpected to be scheduled to receive a second PDSCH with any timerelation to the first PDSCH with a PDCCH that ends also in symbol j froma second CORESET pool; when the UE is scheduled to start receiving afirst PDSCH starting in symbol j by a second PDCCH ending in symbol i,the UE is not expected to be scheduled to receive a PDSCH that overlapswith the first PDSCH with a PDCCH that ends also in symbol j from asecond CORESET pool; or when the UE is scheduled to start receiving afirst PDSCH starting in symbol j by a second PDCCH ending in symbol i,the UE is not expected to be scheduled to receive a PDSCH that does notoverlap with the first PDSCH with a PDCCH that ends also in symbol jfrom a second CORESET pool.
 11. The UE of claim 10, wherein a secondpredetermined rule of the one or more predetermined rules includes atleast one of: when the UE is scheduled to start transmitting a firstPUSCH starting in symbol j by a PDCCH ending in symbol i, the UE is notexpected to be scheduled to transmit a second PUSCH with any timerelation to the first PUSCH with a PDCCH that ends also in symbol j froma second CORESET pool; when the UE is scheduled to start transmitting afirst PDSCH starting in symbol j by a second PDCCH ending in symbol i,the UE is not expected to be scheduled to receive a PUSCH that overlapswith the first PUSCH with a PDCCH that ends also in symbol j from asecond CORESET pool; or when the UE is scheduled to start transmitting afirst PUSCH starting in symbol j by a second PDCCH ending in symbol i,the UE is not expected to be scheduled to transmit a PUSCH that does notoverlap with the first PUSCH with a PDCCH that ends also in symbol jfrom a second CORESET pool.
 12. The UE of claim 5, wherein a firstpredetermined rule of the one or more predetermined rules includes atleast one of: in a common slot, for a PDSCH scheduled by a secondCORESET pool, ACK/NACKs can have any time relationship; or in a commonslot, for a PDSCH scheduled by a second CORESET pool, a CORESET poolhaving a non-zero index value cannot schedule an ACK/NACK earlier than aslot scheduled by a CORESET pool having an index value of 0 forACK/NACK.
 13. An apparatus, comprising: a memory; and a processingelement in communication with the memory, wherein the processing elementis configured to: receive, from a base station, a configurationincluding multiple control resource set (CORESET) pools, wherein eachCORESET pool is associated with an index value; receive multipledownlink control indexes (DCIs); determine a first DCI of the multipleDCIs ends at a first symbol; determine a second DCI of the multiple DCIsends at a second symbol later than the first symbol: and for any twohybrid automatic repeat request (HARD) process identifiers (IDs) in agiven scheduled cell, when the first DCI and the second DCI areassociated with different CORESET pool index values, determine physicaldownlink shared channels (PDSCHs) from CORESETs associated with thefirst and second DCIs can be partially or fully overlapped in time. 14.The apparatus of claim 13, wherein the processing element is furtherconfigured to: for any two HARQ IDs in the given scheduled cell, whenthe first DCI and the second DCI are not associated with differentCORESET pool index values, determine the UE is not expected to bescheduled to receive a PDSCH associated with the second DCI startingearlier than an end of a first PDSCH associated with the first DCI. 15.The apparatus of claim 13, wherein, for each CORESET pool of themultiple CORESET pools, the processing element is further configured to:for frequency division duplexing, monitor one unicast downlinktransmission and one unicast uplink transmission per slot per scheduledcomponent carrier per CORESET pool; and for time division duplexing,monitor one unicast downlink transmission and two unicast uplinktransmissions per slot per scheduled component carrier per CORESET pool.16. The apparatus of claim 13, wherein, for each CORESET pool of themultiple CORESET pools, the processing element is further configured to:for frequency division duplexing, monitor one unicast downlinktransmission and one unicast uplink transmission per component carrierset of monitoring occasions per CORESET pool; and for time divisionduplexing, monitor one unicast downlink transmission and two unicastuplink transmissions per component carrier set of monitoring occasionsper CORESET pool; and monitor two unicast downlink transmissions and oneunicast uplink transmission per component carrier set of monitoringoccasions per CORESET pool.
 17. A non-transitory computer readablememory medium storing program instructions executable by processingcircuitry to cause a user equipment device (UE) to: receive, from a basestation, a configuration including multiple control resource set(CORESET) pools, wherein each CORESET pool is associated with an indexvalue; receive multiple downlink control indexes (DCIs); determine afirst DCI of the multiple DCIs ends at a first symbol; determine asecond DCI of the multiple DCIs ends at a second symbol later than thefirst symbol: and for any two hybrid automatic repeat request (HARQ)process identifiers (IDs) in a given scheduled cell, when the first DCIand the second DCI are associated with different CORESET pool indexvalues, determine physical downlink shared channels (PDSCHs) fromCORESETs associated with the first and second DCIs can be partially orfully overlapped in time.
 18. The non-transitory computer readablememory of claim 17, wherein, for multi-TRP multi-DCI based ultrareliable low latency communication (URLLC), the program instructions arefurther executable to perform at least one of: receiving multiple PDSCHswith a common hybrid automatic repeat request (HARQ) process identifier(ID) overlapping in time; or receiving a second PDSCH with a HARQprocess ID common to a first PDSCH prior to transmission of an ACK/NACKassociated with the first PDSCH.
 19. The non-transitory computerreadable memory of claim 17, wherein the program instructions arefurther executable to cause the UE to: indicate support of single DCImulti-TRP operation modes 1, 2a, 2b, 3, and 4 independently; receive aconfiguration from the base station for a single DCI multi-TRP operationmode that has was indicated as not supported; and operate, in responseto receiving the unsupported configuration, in a fall back mode.
 20. Thenon-transitory computer readable memory of claim 17, wherein the programinstructions are further executable to cause the UE to: indicate that itdoes not support 2 pre-coding matrix indexes (PMIs) sub-bands perchannel quality index (CQI) sub-band for less than 20 PMI sub-bands.